Bug #17032
closed
Upgrade from 1.12.3 to 1.13 - ERROR on missing Puppet bootstrap.cfg file
Description
I got the following ERROR messages when i run the "_foreman-installer --noop --dont-save-answers --verbose_". My Puppet Server is 2.6.0
[ WARN 2016-10-20 10:19:57 verbose] # These normally shouldn't need to be edited if using OS packages [ WARN 2016-10-20 10:19:57 verbose] USER="puppet" [ WARN 2016-10-20 10:19:57 verbose] /Stage[main]/Puppet::Server::Puppetserver/Augeas[puppet::server::puppetserver::jvm]/returns: current_value need_to_run, should be 0 (noop) [ WARN 2016-10-20 10:19:57 verbose] Augeas[puppet::server::puppetserver::bootstrap](provider=augeas): [ WARN 2016-10-20 10:19:57 verbose] --- /etc/sysconfig/puppetserver 2016-09-08 04:32:12.000000000 +0800 [ WARN 2016-10-20 10:19:57 verbose] +++ /etc/sysconfig/puppetserver.augnew 2016-10-20 10:19:57.738995000 +0800 [ WARN 2016-10-20 10:19:57 verbose] @@ -15,7 +15,7 @@ [ WARN 2016-10-20 10:19:57 verbose] CONFIG="/etc/puppetlabs/puppetserver/conf.d" [ WARN 2016-10-20 10:19:57 verbose] [ WARN 2016-10-20 10:19:57 verbose] # Bootstrap path [ WARN 2016-10-20 10:19:57 verbose] -BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/" [ WARN 2016-10-20 10:19:57 verbose] +BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/bootstrap.cfg,/etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/" [ WARN 2016-10-20 10:19:57 verbose] [ WARN 2016-10-20 10:19:57 verbose] SERVICE_STOP_RETRIES=60 [ WARN 2016-10-20 10:19:57 verbose] [ WARN 2016-10-20 10:19:57 verbose] /Stage[main]/Puppet::Server::Puppetserver/Augeas[puppet::server::puppetserver::bootstrap]/returns: current_value need_to_run, should be 0 (noop) [ WARN 2016-10-20 10:19:57 verbose] /Stage[main]/Puppet::Server::Puppetserver/File[/etc/puppetlabs/puppetserver/bootstrap.cfg]/ensure: current_value absent, should be file (noop) [ERROR 2016-10-20 10:19:57 verbose] /Stage[main]/Puppet::Server::Puppetserver/File_line[ca_enabled]: Could not evaluate: No such file or directory @ rb_sysopen - /etc/puppetlabs/puppetserver/bootstrap.cfg [ERROR 2016-10-20 10:19:57 verbose] /usr/share/foreman-installer/modules/stdlib/lib/puppet/provider/file_line/ruby.rb:39:in `readlines' [ERROR 2016-10-20 10:19:57 verbose] /usr/share/foreman-installer/modules/stdlib/lib/puppet/provider/file_line/ruby.rb:39:in `lines' [ERROR 2016-10-20 10:19:57 verbose] /usr/share/foreman-installer/modules/stdlib/lib/puppet/provider/file_line/ruby.rb:6:in `exists?' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property/ensure.rb:81:in `retrieve' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1069:in `retrieve' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1097:in `retrieve_resource' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:300:in `from_resource' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in `evaluate' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:224:in `apply' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:240:in `eval_resource' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `call' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block (2 levels) in evaluate' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:386:in `block in thinmark' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:385:in `thinmark' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block in evaluate' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:137:in `as_logging_destination' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in `override' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in `override' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:344:in `run' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' [ERROR 2016-10-20 10:19:57 verbose] /opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
Similar to http://projects.theforeman.org/issues/15132
Updated by Dominic Cleal over 7 years ago
- Project changed from Foreman to Installer
- Category changed from PuppetCA to Foreman modules
- Status changed from New to Feedback
The file is missing because you're running in --noop mode. Check the previous line and you will see it's due to be created:
[ WARN 2016-10-20 10:19:57 verbose] /Stage[main]/Puppet::Server::Puppetserver/File[/etc/puppetlabs/puppetserver/bootstrap.cfg]/ensure: current_value absent, should be file (noop)Try running the installer.
Updated by Anandharaj Subramaniam over 7 years ago
Running just the foreman-installer is successful but the Puppet Server unable to start. Then i found this https://groups.google.com/forum/#!topic/foreman-users/w4N08K83Ubs and run the installer again with --puppet-server-puppetserver-version=2.6.0 option.
I guess this should be stated in the document.
Also, the bootstrap.cfg file is depreciated in latest PupperServer. Any reason why this being created by Foreman?
Updated by Dominic Cleal over 7 years ago
Anandharaj Subramaniam wrote:
Running just the foreman-installer is successful but the Puppet Server unable to start. Then i found this https://groups.google.com/forum/#!topic/foreman-users/w4N08K83Ubs and run the installer again with --puppet-server-puppetserver-version=2.6.0 option.
I guess this should be stated in the document.
This should only need to be changed if you've also upgraded Puppet Server. It shouldn't be necessary if the version of Puppet Server hasn't changed since initial installation.
Also, the bootstrap.cfg file is depreciated in latest PupperServer. Any reason why this being created by Foreman?
With puppetserver-version set to 2.6.0, it shouldn't be created any more - only when being configured for 2.4 or lower, or 2.4/2.5 compatibility mode (2.4.99). If you've upgraded from 1.12 then the value may have been set to 2.4.99, which was the current version at release.
Updated by Anandharaj Subramaniam over 7 years ago
Dominic Cleal wrote:
This should only need to be changed if you've also upgraded Puppet Server. It shouldn't be necessary if the version of Puppet Server hasn't changed since initial installation.
Noted. The PuppetServer might get updated when we run yum upgrade. Perhaps, it is good if PuppetServer version can be validated every time run the foreman-installer
With puppetserver-version set to 2.6.0, it shouldn't be created any more - only when being configured for 2.4 or lower, or 2.4/2.5 compatibility mode (2.4.99). If you've upgraded from 1.12 then the value may have been set to 2.4.99, which was the current version at release.
Noted on this. The file seems created when i first run the foreman-installer command without specifying the PeppetServer version.
Updated by Anonymous