Description of problem: Nodes are shared by all plans, but if different plans define different roles, the nodes that assigned to those roles will appear as "not assigned" in plans that don't recognize them. Version-Release number of selected component (if applicable): openstack-tripleo-ui-1.0.5-1.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Upload a plan with custom roles 2. Assign nodes to these roles and check in the Nodes page that the assigned role is displayed on the nodes 3. Switch to another active plan 4. Look in the Nodes page again Actual results: The nodes appear as "not assigned". We could have a collision here if the same nodes are assigned to different roles in different plans. Expected results: The assigned role should be displayed even if such a role doesn't exist in the plan that is currently active.
I filed the bug upstream. I also strongly disagree with the "urgent" severity FWIW. It's annoying and confusing and needs to be fixed, ideally soon, but it's not blocking any major workflow and easy to work around. As far as I could see, the node assigned to a custom-role is not shown in the Deployment Page if the role isn't defined so there shouldn't be space for a collision.
upstream fix was merged
The flag are not quite right, the fix merged in Ocata aka 11. Either we need to change the flags/target version, or switch the status back to ON_DEV until the backport is merged.
Thanks Julie. Changing back to ON_DEV
Stable/newton backport merged.
updated to include only stable/newton patch
It works in OSP11 and needs to be tested in OSP10 z3. There is only a small problem that you can't un-assign a node from a custom role, when you're in a plan that doesn't feature this role (you won't find a role assignment card for it in the deployment page).
What happens if you delete the plan with the custom roles? You can't un-assign nodes from a role that doesn't exits in any plan, which makes these nodes unrecoverable for further use any more.
Verified in puddle 2017-04-10.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1587