Here is how the plan is specified for the current openstack overcloud commands: [centos@undercloud ~]$ openstack help overcloud deploy optional arguments: --plan-uuid PLAN_UUID The UUID of the Tuskar plan to deploy. [centos@undercloud ~]$ openstack help overcloud scale stack positional arguments: plan Name or ID of tuskar plan to scale (default=Env: OVERCLOUD_PLAN_NAME) [centos@undercloud ~]$ openstack help overcloud update stack --plan PLAN Name or ID of tuskar plan to scale (default=Env: OVERCLOUD_PLAN_NAME) [centos@undercloud ~]$ openstack help overcloud node delete --plan PLAN Name or ID of tuskar plan to scale (default=Env: OVERCLOUD_PLAN_NAME) So these commands can be made consistent, I'd like to suggest that "overcloud deploy" and "overcloud scale stack" adopt the --plan argument, which accepts a plan name _or_ UUID.
Fix submitted to gerrithub. This updates `overcloud deploy` https://review.gerrithub.io/#/c/237062/ Updating `overcloud scale stack` is less trivial as the logic behind it in tripleo-common doesn't support deploying a non-Tuskar stack.
Opened a new bug for openstack overcloud scale stack. https://bugzilla.redhat.com/show_bug.cgi?id=1233631
The overcloud scale stack command doesn't need to be updated as it will be removed: https://bugzilla.redhat.com/show_bug.cgi?id=1233201
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.