Issue #16651 has been updated by Andrew Parker.
Target version deleted (3.0.x)
Bug #16651: Installing the cloud provisioner module breaks the node subcommand
https://projects.puppetlabs.com/issues/16651#change-80555
Author: Jeff McCune
Status: Duplicate
Issue #16651 has been updated by Josh Cooper.
Andrew Parker wrote:
> There is a bug (#15165) filed against cloud provisioner to fix the `--tags`
> option. Changing from an error to a warning might be a good change though, so
> that we don't continually hit this.
Yep, all settings are automagi
Issue #16651 has been updated by Andrew Parker.
There is a bug (#15165) filed against cloud provisioner to fix the `--tags`
option. Changing from an error to a warning might be a good change though, so
that we don't continually hit this. I just don't know what kind of unintended
consequences
Issue #16651 has been updated by Josh Cooper.
And the trace:
Error: Could not autoload puppet/face/node_aws/bootstrap: "--tags=": already
defined in puppet
/Users/josh/work/puppet/lib/puppet/interface/option.rb:31:in `initialize'
/Users/josh/work/puppet/lib/puppet/interface/option.rb:13:in `e
Issue #16651 has been updated by Josh Cooper.
The fix in progress for #7136 adds the current environment's modulepath to the
$LOAD_PATH prior to requiring the face. This enables the face application to
require utility code (require 'puppet/cloudpack'). However, we are now running
into #13898,
Issue #16651 has been updated by Jeff McCune.
Keywords set to faces node face subcommand cloud_provisioner
Bug #16651: Installing the cloud provisioner module breaks the node subcommand
https://projects.puppetlabs.com/issues/16651#change-72088
Author: J
Issue #16651 has been updated by Jeff McCune.
# Trace
root@pe-centos6:~# puppet help node --trace
Error: Could not autoload puppet/face/node/classify: no such file to load --
puppet/cloudpack
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
/usr/lib/ruby/si
Issue #16651 has been updated by Jeff McCune.
I've also filed #16651 which specifically calls out the bug we've introduced
(or rather failed to fix?) in 3.0.0.
I think a new bug is warranted because we're explicitly breaking existing
functionality on the node subcommand, which is a subtlety n
