[chef] strange node attribute problem

[John Alberts < >]

I have a strange problem with using a node attribute that recently had the value changed.

I have a ruby_block resource that sets a node attribute.  The following mount resource uses that node attribute, but it is getting the old value of that node attribute, not the new value that was just set by the previous ruby_block.  I've tried adding a node.save in that ruby_block, but the mount resource still gets the old attribute value.  Of course, since I did a node.save, the mount resource gets the new value because it was save on the previous failed chef run.

Is this expected behavior?  I've never noticed this before.

Here is the section of code I'm having the issue with.  It's the node[:ebs][:devicetomount] attribute that I'm having trouble with.

Original pastebin here: http://pastebin.com/XmQ2KtBn

Thanks

John

1.   ruby_block "Create or attach LVM volume out of #{raid_device}" do
2.     block do
3.       BlockDevice.create_lvm(raid_device, options)
4.       node.set[:ebs][:devicetomount] = node[:ebs][:lvm_device]
5.       node.save unless Chef::Config[:solo]
6.     end
7.     only_if { options[:uselvm] }
8.     action :create
9.   end
10.  
11.   mount options[:mount_point] do
12.     fstype options[:fstype]
13.     device node[:ebs][:devicetomount]
14.     options "noatime"
15.     not_if do
16.       File.read('/etc/mtab').split("\n").any?{|line| line.match(" #{options[:mount_point]} ")}
17.     end
18.   end