You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you plug a disk to a node after having allocated the node, then crowbar will never know about the disk.
The chef-client run that occurs every 15 minutes will update node["block_device"], but the code that translates node["block_device"] to node["crowbar"]["disks"] is done in the transition method of deployer_service.rb (barclamp-deployer).
The issue is that all the barclamps that want to know about the disks will look at node["crowbar"]["disks"] because there's some additional needed information (and unneeded devices listed in block_device are filtered).
This can be worked around by forcing a transition:
If you plug a disk to a node after having allocated the node, then crowbar will never know about the disk.
The chef-client run that occurs every 15 minutes will update node["block_device"], but the code that translates node["block_device"] to node["crowbar"]["disks"] is done in the transition method of deployer_service.rb (barclamp-deployer).
The issue is that all the barclamps that want to know about the disks will look at node["crowbar"]["disks"] because there's some additional needed information (and unneeded devices listed in block_device are filtered).
This can be worked around by forcing a transition:
But that's obviously suboptimal.
The text was updated successfully, but these errors were encountered: