Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

embedded knife commands show warnings #3329

Open
marcparadise opened this issue May 24, 2022 · 1 comment
Open

embedded knife commands show warnings #3329

marcparadise opened this issue May 24, 2022 · 1 comment
Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Status: move to jira Triage: Confirmed Indicates and issue has been confirmed as described.

Comments

@marcparadise
Copy link
Member

marcparadise commented May 24, 2022 •
edited
Loading

Chef Server Version

v14.13.42

Running any knife command on CIS 14.13.42+ outputs warnings. Let's make it not do that. It looks like we have two versions of chef-vault shipping (4.1.5, 4.1.4) and they are managing to both get loaded.

knife node list
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:18: warning: already initialized constant ChefVault::VERSION
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.4/lib/chef-vault/version.rb:18: warning: previous definition of VERSION was here
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::MAJOR
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.4/lib/chef-vault/version.rb:19: warning: previous definition of MAJOR was here
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::MINOR
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.4/lib/chef-vault/version.rb:19: warning: previous definition of MINOR was here
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::TINY
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.4/lib/chef-vault/version.rb:19: warning: previous definition of TINY was here
@marcparadise marcparadise added the Status: Untriaged An issue that has yet to be triaged. label May 24, 2022
@marcparadise marcparadise added Triage: Confirmed Indicates and issue has been confirmed as described. Aspect: Packaging Distribution of the projects 'compiled' artifacts. and removed Status: Untriaged An issue that has yet to be triaged. labels Jun 7, 2022
@ineednewpajamas
Copy link

Issue persists in chef-server-core-15.0.9 but with updated versions

/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:18: warning: already initialized constant ChefVault::VERSION
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:18: warning: previous definition of VERSION was here
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::MAJOR
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19: warning: previous definition of MAJOR was here
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::MINOR
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19: warning: previous definition of MINOR was here
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::TINY
/opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19: warning: previous definition of TINY was here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Status: move to jira Triage: Confirmed Indicates and issue has been confirmed as described.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marcparadise @ineednewpajamas