Description of problem:
When I try to assign nodes on a non-default plan, the profile gets added to the node correctly but the node count wrongly gets updated for the 'overcloud' default plan, *not* the plan currently activated.
It means only the default of 1 controller and 1 compute will ever be deployed for non-default plans. This may also cause issues later on if people use the CLI to scale up/down the default plan.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new plan, e.g. test
2. Click on the new plan to "activate" it and got to the "Deployment Plan" page
3. On the CLI, look at the mistral environments for both 'overcloud' and 'test', confirm nothing is set in the parameters_defaults ($ mistral environment-get <plan_name>)
4. On the UI, assign a node to 'Ceph storage'
5. The CephStorageCount for 'overcloud' was updated to 1, the 'test' environment didn't change.
5. The CephStorageCount for 'test' got updated in the Mistral environment.
This is possibly related to the larger node assignment/tagging splitting (tracked upstream at https://bugs.launchpad.net/tripleo/+bug/1640103) though it'd be good to get a band-aid for this while waiting for the better, possibly-not-easily-backportable fix.
There is a workaround: On the deployment page in the UI, editing the overall Deployment Configuration and navigating to the Parameters, it is possible to manually update the node count for the main roles (CephStoragecCount, ControllerCount, etc).
I don't think this is a release blocker, as it doesn't affect the default plan and there is a workaround. However, I think it needs to be documented in a release note, and hopefully fixed shortly.
See bug 1395755 (especially comments 3 to 7) to see additional information on the bug's effect.
Updating the doc text to mark this as a known issue, in case the upstream patches don't merge in time for GA.
Last backport proposed upstream.
All the upstream fixes have merged in stable/newton.
identified external tracker patches are included in specified Fixed in versions
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.