Undercloud preflight checks should log what they are doing
Bug #1783787 reported by
Cédric Jeanneret
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Cédric Jeanneret | ||
Bug Description
Currently the preflight checks¹ just don't say anything - it takes time, and people don't know what's going on.
A nice output saying something like "Ensuring <thing> is OK... [OK]" or the like would be really nice.
| tags: | added: ux |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-tripleoclient (master) | #1 |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/python-tripleoclient 10.5.0 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 766b3e3ddacb6b2
Author: Cédric Jeanneret <email address hidden>
Date: Thu Jul 26 17:29:16 2018 +0200
Add some logging for the preflight checks
Currently, the preflight checks are run without any output.
This can be misleading, especially if we get an error on one
of the checks - no real way to know WHAT failed in the current
situation.
This easy log output helps the operator to know what's going on.
Change-Id: Ifbdbdb37431ad2
Closes-Bug: 1783787