Issue #7746 has been updated by James Turnbull. Status changed from Merged - Pending Release to Closed
---------------------------------------- Bug #7746: starting puppet master fails on ruby 1.8.7 https://projects.puppetlabs.com/issues/7746 Author: Dominic Maraglia Status: Closed Priority: Normal Assignee: Daniel Pittman Category: server Target version: 2.7.0 Affected Puppet version: 2.7.0rc1 Keywords: ruby 1.8.7 master fail start Branch: Starting puppet master fails when installed with ruby 1.8.7 error output on puppet master node: <pre> root@centos-55-64-1 ~]# puppet master --certdnsnames="puppet:$(hostname -s):$(hostname -f)" --verbose --noop Could not prepare for execution: Got 1 failure(s) while initializing: change from absent to file failed: Could not set 'file on ensure: No such file or directory - /root/groupserviceownerservicemode488default$vardir/logdescThe Puppet log directory./masterhttp.log [root@centos-55-64-1 ~]# puppet master --certdnsnames="puppet:$(hostname -s):$(hostname -f)" --verbose Could not prepare for execution: Got 1 failure(s) while initializing: change from absent to file failed: Could not set 'file on ensure: No such file or directory - /root/groupserviceownerservicemode488default$vardir/logdescThe Puppet log directory./masterhttp.log [root@centos-55-64-1 ~]# puppet master --certdnsnames="puppet:$(hostname -s):$(hostname -f)" Could not prepare for execution: Got 1 failure(s) while initializing: change from absent to file failed: Could not set 'file on ensure: No such file or directory - /root/groupserviceownerservicemode488default$vardir/logdescThe Puppet log directory./masterhttp.log [root@centos-55-64-1 ~]# puppet master Could not prepare for execution: Got 1 failure(s) while initializing: change from absent to file failed: Could not set 'file on ensure: No such file or directory - /root/groupserviceownerservicemode488default$vardir/logdescThe Puppet log directory./masterhttp.log </pre> Config info <pre> Platform for centos-55-386-1 centos-5-i386 Platform for centos-55-64-1 centos-5-x86_64 Role for centos-55-386-1 agent Role for centos-55-64-1 master Ruby version for centos-55-386-1 ruby 1.8.7 (2011-02-18 patchlevel 334) [i686-linux] Ruby version for centos-55-64-1 ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux] Config Key|Val: puppet_ver "a23cfd869f90ae4456dded6e5a1c82719b128f01" Config Key|Val: version {:puppet=>"2.7.0rc3-29-ga23cfd8", :facter=>"1.5.8"} Config Key|Val: facter_ver "1.5.8" </pre> I've tracked down the failure to this commit: <pre> commit a23cfd869f90ae4456dded6e5a1c82719b128f01 Author: Daniel Pittman <[email protected]> Date: Wed Jun 1 11:04:18 2011 -0700 (#7177) Deprecate implicit 'puppet apply' for 2.7.0 Back in prehistory (eg: 0.25 era), 'puppet' was the name for the agent, and could be used directly to apply a manifest as well as to communicate with the puppet master process. During the 2.6 series we moved to a single binary, but continued to support older scripts by detecting invocations that looked like the traditional scripting uses and implicitly turning those into a call to 'puppet apply'. Now, with the 2.7.0 release, we are moving to deprecate that behaviour. We still do the same detection, and still run the old manifests, but we now emit a deprecation warning directing people to use 'puppet apply' directly. We intend to remove the behaviour entirely in the 2.8 release, which also paves the way to nicer handling of the command line. </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
