When running 'openstack overcloud update stack -i' you get the following output:
$ openstack overcloud update stack -i overcloud
Started Mistral Workflow tripleo.package_update.v1.package_update_plan. Execution ID: dc76a26d-67bc-49a2-b48e-5ddb0b2b97e9
Waiting for messages on queue 'ee3b698b-e0cf-4e75-a3e2-57b8a384ba6b' with no timeout.
IN_PROGRESS
WAITING
not_started: [u'overcloud-controller-0', u'overcloud-controller-1']
on_breakpoint: [u'overcloud-controller-2', u'overcloud-novacompute-0']
Breakpoint reached, continue? Regexp or Enter=proceed (will clear 39d3fdd2-1178-4c10-a4f3-fc1cccf2c1dc), no=cancel update, C-c=quit interactive mode:
We could improve the messages here somewhat. For example:
- "Will clear 39d3fdd2-1178-4c10-a4f3-fc1cccf2c1dc" means absolutely nothing to average joe
- Also the difference between not_started and on_breakpoint are completely not obvious (ospecially because I expected to have all nodes except one on 'not_started')
- Later in the process when all nodes are 'on_completed' we should print which heat step we are running instead of a bunch of IN_PROGRESS.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE