Closed homeyjd closed 9 years ago
For reference, I have only tested this against edge Chef v11.8.2.
That's strange. Will try this out myself since this does not look like an expected behaviour.
I setup a test kitchen box with the following:
The converge ran successfully without any errors:
[...]
[2014-11-04T09:46:43+00:00] INFO: Chef Run complete in 40.274098378 seconds
[2014-11-04T09:46:43+00:00] INFO: Running report handlers
[2014-11-04T09:46:43+00:00] INFO: Report handlers complete
Chef Client finished, 10 resources updated
Finished converging <default-centos-70> (1m20.21s).
[...]
Any more details on this issue? I ran an entire converge across all platforms and all converge runs ended successfully. Even a second run did not throw any errors.
Wow, thanks for getting to this so quickly. My action steps that produced the error:
sudo service vsftpd start
would fail as would sudo vsftpd
. Both would exit status=1 without any syslog or file log messages. Never did find the exact issue though the upgrade broke 2 systems -- very frustrating. Sorry I totally forgot to merge this one! My bad :-/
When service is in error state, system will attempt to restart vsftpd before updating /etc/vsftpd.conf. Chef will forever fail. Updated recipes/_configure.rb to put service description below template calls. The "notifies" directive still works correctly as it appears the string 'service[vsftpd]' is resolved during the run-phase instead of compile-phase.