I doubt it's limited to remote_file only (you showed it's an issue with the file resource as well) I just didn't have time to figure out if it's affecting notifications in general or only specific resources.
It's a big blocker for us as well. Had to squash installing 10.10 until it gets worked out.
MGOn Fri, May 25, 2012 at 1:56 PM, John Dyer < " target="_blank"> > wrote:
Yikes, this looks like a blocker for me using 10.10... I rely on notifications in remote_files resources like its going out of style :) Nice catch Mike!On Fri, May 25, 2012 at 4:49 PM, Michael Glenney < " target="_blank"> > wrote:
I submitted a bug for that last week. You can track it here: http://tickets.opscode.com/browse/CHEF-3135
MGOn Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique < " target="_blank"> > wrote:
Hi,I am running in to an odd problem with notification in Chef 10.10, it seems suddenly this block of code is not working as expected:execute "set-hostname" docommand "hostname --file /etc/hostname"action :nothingendfile "/etc/hostname" docontent "#{new_hostname}"notifies :run, "execute[set-hostname]", :immediatelyendIn the chef log I get this:.compute-1.amazonaws.com [Fri, 25 May 2012 20:13:57 +0000] INFO: Processing execute[set-hostname] action nothing (gridiron-deploy::default line 44) .compute-1.amazonaws.com [Fri, 25 May 2012 20:13:57 +0000] INFO: Processing file[/etc/hostname] action create (gridiron-deploy::default line 49) .compute-1.amazonaws.com [Fri, 25 May 2012 20:13:57 +0000] INFO: file[/etc/hostname] backed up to /var/chef/backup/etc/hostname.chef-20120525201357 .compute-1.amazonaws.com [Fri, 25 May 2012 20:13:57 +0000] INFO: file[/etc/hostname] contents updatedBut when I login to the box the hostname is not set. Inspecting /etc/hostname show its populated with the correct info and running hostname --file /etc/hostname on the box works but it seems via Chef its no go. On a local box using shef it works fine. Beside me getting hack-y and making it a bash command any ideas?Zuhaib
Archive powered by MHonArc 2.6.16.