Description of problem:
A deployment where introspection fails produces a subdued message in one line, which quickly scrolls on, and end in "Discovery completed."
This might be missed by the deployer and he will move on, to an overcloud setup which will fail.
Version-Release number of selected component (if applicable):
[stack@undercloud72 ~]$ rhos-release -v
Steps to Reproduce:
1. run instrospection where one of the nodes will fail
2. watch stdout
Setting available nodes to manageable...
Starting introspection of node: e06fc6e3-d90d-4a8d-8ef8-748f33edf975
Waiting for discovery to finish...
Discovery for UUID e06fc6e3-d90d-4a8d-8ef8-748f33edf975 finished successfully.
Setting manageable nodes to available...
Node e06fc6e3-d90d-4a8d-8ef8-748f33edf975 has been set to available.
If a fault shows up somewhere in the middle, and there are many nodes, the error can only be seen when checking the status or scrolling back over the stdout.
Either output the full ironic status after introspection, or if there had been any errors, throw them into stdout after "Discovery completed." for better user visibility
This might also be solved by stressing the need to verify the introspection results in the docs, though it will be a better UX if we alert on failures as well.
Hi Dmitry, Can we get any simple changes to the output in time for 7.3?
Either way, an update to the docs would make sense,
Hi, sorry for the late answer. It could be a simple change, but I'm not really fond of making any changes to OSPd7 except for critical fixes.
Dmitry, can you please doc_text this for 7.3 please?
Done (no clues what to put in the "result" field)
Ifwe're going for a doc change, I'd say tell the user to run ironic node-list and verify node statuses are as expected post-introspection