Problem with notifies


#1

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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In 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 updated

But 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


#2

I submitted a bug for that last week. You can track it here:
http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <
zuhaib.siddique@leapfile.com> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In 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 updated

But 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


#3

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 :slight_smile:
Nice catch Mike!

On Fri, May 25, 2012 at 4:49 PM, Michael Glenney mike.glenney@gmail.comwrote:

I submitted a bug for that last week. You can track it here:
http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <
zuhaib.siddique@leapfile.com> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In 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 updated

But 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


#4

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.

MG

On Fri, May 25, 2012 at 1:56 PM, John Dyer johntdyer@gmail.com 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 :slight_smile:
Nice catch Mike!

On Fri, May 25, 2012 at 4:49 PM, Michael Glenney mike.glenney@gmail.comwrote:

I submitted a bug for that last week. You can track it here:
http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <
zuhaib.siddique@leapfile.com> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In 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 updated

But 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


#5

Bump! Same issue with our organization.

On Fri, May 25, 2012 at 4:00 PM, Michael Glenney mike.glenney@gmail.comwrote:

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.

MG

On Fri, May 25, 2012 at 1:56 PM, John Dyer johntdyer@gmail.com 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 :slight_smile:
Nice catch Mike!

On Fri, May 25, 2012 at 4:49 PM, Michael Glenney mike.glenney@gmail.comwrote:

I submitted a bug for that last week. You can track it here:
http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <
zuhaib.siddique@leapfile.com> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In 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 updated

But 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


Charles Sullivan
charlie.sullivan@gmail.com


#6

Gah! This is going to suck… Going to need to tweak our chef_client cookbook to lock to older version till this is fixed (not fun)
On May 25, 2012, at 1:49 PM, Michael Glenney mike.glenney@gmail.com wrote:

I submitted a bug for that last week. You can track it here: http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique zuhaib.siddique@leapfile.com 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In 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 updated

But 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


#7

On Friday, May 25, 2012 at 2:32 PM, Zuhaib Siddique wrote:

Gah! This is going to suck… Going to need to tweak our chef_client cookbook to lock to older version till this is fixed (not fun)
On May 25, 2012, at 1:49 PM, Michael Glenney <mike.glenney@gmail.com (mailto:mike.glenney@gmail.com)> wrote:

I submitted a bug for that last week. You can track it here: http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <zuhaib.siddique@leapfile.com (mailto:zuhaib.siddique@leapfile.com)> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In the chef log I get this:

.compute-1.amazonaws.com (http://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 (http://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 (http://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 (http://compute-1.amazonaws.com/) [Fri, 25 May 2012 20:13:57 +0000] INFO: file[/etc/hostname] contents updated

But 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
Hey guys, you’re only seeing this bug on resources that manage files?

I’m pretty sure the problem is here:
https://github.com/opscode/chef/blob/master/chef/lib/chef/mixin/enforce_ownership_and_permissions.rb#L34

Can you confirm that changing that line to

    new_resource.updated_by_last_action(true) if access_controls.modified?

fixes it?

Thanks in advance


Dan DeLeo


#8

On Friday, May 25, 2012 at 3:10 PM, Daniel DeLeo wrote:

On Friday, May 25, 2012 at 2:32 PM, Zuhaib Siddique wrote:

Gah! This is going to suck… Going to need to tweak our chef_client cookbook to lock to older version till this is fixed (not fun)
On May 25, 2012, at 1:49 PM, Michael Glenney <mike.glenney@gmail.com (mailto:mike.glenney@gmail.com)> wrote:

I submitted a bug for that last week. You can track it here: http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <zuhaib.siddique@leapfile.com (mailto:zuhaib.siddique@leapfile.com)> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In the chef log I get this:

.compute-1.amazonaws.com (http://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 (http://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 (http://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 (http://compute-1.amazonaws.com/) [Fri, 25 May 2012 20:13:57 +0000] INFO: file[/etc/hostname] contents updated

But 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

Hey guys, you’re only seeing this bug on resources that manage files?

I’m pretty sure the problem is here:
https://github.com/opscode/chef/blob/master/chef/lib/chef/mixin/enforce_ownership_and_permissions.rb#L34

Can you confirm that changing that line to

new_resource.updated_by_last_action(true) if access_controls.modified?

fixes it?

Thanks in advance


Dan DeLeo

I committed a fix for this in master. Can you guys test and confirm it fixes your issue?

Feel free to ask if you need help building chef from master.

Thanks in advance,


Dan DeLeo


#9

Hey Dan,

I tested master yesterday and it resolves the issue described in CHEF-3135.

Thanks,


Hector

On Sat, May 26, 2012 at 3:21 PM, Daniel DeLeo dan@kallistec.com wrote:

On Friday, May 25, 2012 at 3:10 PM, Daniel DeLeo wrote:

On Friday, May 25, 2012 at 2:32 PM, Zuhaib Siddique wrote:

Gah! This is going to suck… Going to need to tweak our chef_client cookbook to lock to older version till this is fixed (not fun)
On May 25, 2012, at 1:49 PM, Michael Glenney <mike.glenney@gmail.com (mailto:mike.glenney@gmail.com)> wrote:

I submitted a bug for that last week. You can track it here: http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <zuhaib.siddique@leapfile.com (mailto:zuhaib.siddique@leapfile.com)> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In the chef log I get this:

.compute-1.amazonaws.com (http://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 (http://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 (http://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 (http://compute-1.amazonaws.com/) [Fri, 25 May 2012 20:13:57 +0000] INFO: file[/etc/hostname] contents updated

But 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

Hey guys, you’re only seeing this bug on resources that manage files?

I’m pretty sure the problem is here:
https://github.com/opscode/chef/blob/master/chef/lib/chef/mixin/enforce_ownership_and_permissions.rb#L34

Can you confirm that changing that line to

new_resource.updated_by_last_action(true) if access_controls.modified?

fixes it?

Thanks in advance


Dan DeLeo

I committed a fix for this in master. Can you guys test and confirm it fixes your issue?

Feel free to ask if you need help building chef from master.

Thanks in advance,


Dan DeLeo


#10

On Saturday, May 26, 2012 at 6:30 PM, Hector Castro wrote:

Hey Dan,

I tested master yesterday and it resolves the issue described in CHEF-3135.

Thanks,


Hector

Thanks for testing. <3


Dan DeLeo

On Sat, May 26, 2012 at 3:21 PM, Daniel DeLeo <dan@kallistec.com (mailto:dan@kallistec.com)> wrote:

On Friday, May 25, 2012 at 3:10 PM, Daniel DeLeo wrote:

On Friday, May 25, 2012 at 2:32 PM, Zuhaib Siddique wrote:

Gah! This is going to suck… Going to need to tweak our chef_client cookbook to lock to older version till this is fixed (not fun)
On May 25, 2012, at 1:49 PM, Michael Glenney <mike.glenney@gmail.com (mailto:mike.glenney@gmail.com)> wrote:

I submitted a bug for that last week. You can track it here: http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <zuhaib.siddique@leapfile.com (mailto:zuhaib.siddique@leapfile.com)> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In the chef log I get this:

.compute-1.amazonaws.com (http://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 (http://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 (http://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 (http://compute-1.amazonaws.com/) [Fri, 25 May 2012 20:13:57 +0000] INFO: file[/etc/hostname] contents updated

But 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

Hey guys, you’re only seeing this bug on resources that manage files?

I’m pretty sure the problem is here:
https://github.com/opscode/chef/blob/master/chef/lib/chef/mixin/enforce_ownership_and_permissions.rb#L34

Can you confirm that changing that line to

new_resource.updated_by_last_action(true) if access_controls.modified?

fixes it?

Thanks in advance


Dan DeLeo

I committed a fix for this in master. Can you guys test and confirm it fixes your issue?

Feel free to ask if you need help building chef from master.

Thanks in advance,


Dan DeLeo


#11

Hey Guys,

So please excuse what I guess could be a stupid question, but what now…
Seems like we have a confirmed fix for 10.10, how do implement it ? Does
OpsCode do a hot fix? this seems like a pretty critical bug to me…

-John

On Sun, May 27, 2012 at 11:23 PM, Daniel DeLeo dan@kallistec.com wrote:

On Saturday, May 26, 2012 at 6:30 PM, Hector Castro wrote:

Hey Dan,

I tested master yesterday and it resolves the issue described in
CHEF-3135.

Thanks,


Hector

Thanks for testing. <3


Dan DeLeo

On Sat, May 26, 2012 at 3:21 PM, Daniel DeLeo <dan@kallistec.com(mailto:
dan@kallistec.com)> wrote:

On Friday, May 25, 2012 at 3:10 PM, Daniel DeLeo wrote:

On Friday, May 25, 2012 at 2:32 PM, Zuhaib Siddique wrote:

Gah! This is going to suck… Going to need to tweak our chef_client
cookbook to lock to older version till this is fixed (not fun)

On May 25, 2012, at 1:49 PM, Michael Glenney <
mike.glenney@gmail.com (mailto:mike.glenney@gmail.com)> wrote:

I submitted a bug for that last week. You can track it here:
http://tickets.opscode.com/browse/CHEF-3135

MG

On Fri, May 25, 2012 at 1:32 PM, Zuhaib Siddique <
zuhaib.siddique@leapfile.com (mailto:zuhaib.siddique@leapfile.com)> 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” do
command "hostname --file /etc/hostname"
action :nothing
end

file “/etc/hostname” do
content "#{new_hostname}"
notifies :run, “execute[set-hostname]”, :immediately
end

In the chef log I get this:

.compute-1.amazonaws.com (http://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(
http://compute-1.amazonaws.com/) [Fri, 25 May 2012 20:13:57 +0000] INFO:
Processing file[/etc/hostname] action create (gridiron-deploy::default line

  1. .compute-1.amazonaws.com (http://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(
    http://compute-1.amazonaws.com/) [Fri, 25 May 2012 20:13:57 +0000] INFO:
    file[/etc/hostname] contents updated

But 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

Hey guys, you’re only seeing this bug on resources that manage files?

I’m pretty sure the problem is here:

https://github.com/opscode/chef/blob/master/chef/lib/chef/mixin/enforce_ownership_and_permissions.rb#L34

Can you confirm that changing that line to

new_resource.updated_by_last_action(true) if
access_controls.modified?

fixes it?

Thanks in advance


Dan DeLeo

I committed a fix for this in master. Can you guys test and confirm it
fixes your issue?

Feel free to ask if you need help building chef from master.

Thanks in advance,


Dan DeLeo


#12

On Tuesday, May 29, 2012 at 7:32 PM, John Dyer wrote:

Hey Guys,

So please excuse what I guess could be a stupid question, but what now… Seems like we have a confirmed fix for 10.10, how do implement it ? Does OpsCode do a hot fix? this seems like a pretty critical bug to me…

-John
We should be shipping a RC with fixes for all known regressions in 0.10.10 very soon, possibly today.


Dan DeLeo