-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
neutron recipes on compute nodes should not look at attributes from neutron-server nodes #11
Comments
If you look at the neutron cookbook, you'll see some recipes which are run on compute nodes too. These ones are the problematic ones. We do something like |
Note that this is a bit of a special case: usually, the data bag config item that you backported would be enough; but the problem is that the recipes need to look at, basically, all attributes of the proposal. Which is way more than what the data bag config item contains. Of course, one alternative is to make the data bag config item contain a copy of the attributes. |
@mkoderer this is a true issue, but also a very edge case that wouldn't occur again unless more attributes are added to the neutron barclamp. I'm tempted to drop the critical tag here. |
It could be that an attribute gets added in a migration to the neutron proposal, and this will become visible on the neutron-server node only when chef has run. However, if chef runs on compute nodes first, it will not find the attribute. This could result in the wrong config on the compute nodes for a period of time.
The fix is to adopt the data bag config item work, and extend it (see crowbar#718)
Backport Databag work
Fix the issue
The text was updated successfully, but these errors were encountered: