Bug 1412351 - [RFE] [Ironic] Need to have a way to check the progress of a cleaning process. May take a very long time.
Summary: [RFE] [Ironic] Need to have a way to check the progress of a cleaning process...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: mlammon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-11 20:18 UTC by Alexander Chuzhoy
Modified: 2020-04-27 01:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2017-01-11 20:18:19 UTC
openstack-ironic: [RFE] Need to have a way to check the progress of a cleaning process. May take a very long time.

ATM, there's no way to check how long the cleaning process will take. Need to have a command that will show a completed percentage:


I can only see that the provisioning state is "clean wait":

[stack@undercloud ~]$ ironic node-list
+--------------------------------------+--------+---------------+-------------+--------------------+-------------+
| UUID                                 | Name   | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+--------+---------------+-------------+--------------------+-------------+
| 74df922c-84c6-44c5-8f48-5cb3273fbc68 | node-0 | None          | power on    | clean wait         | False       |
+--------------------------------------+--------+---------------+-------------+--------------------+-------------+

Comment 1 Dmitry Tantsur 2017-01-12 11:32:51 UTC
Cleaning up release flags, as it's not a big priority for us, and I doubt it's going to hit Pike (if implemented at all). Note that you can track the clean steps in the driver_internal_info field, but if a clean step (like erase_devices) just blocks execution for an hour (which is what it does), I'm not sure how we report it.


Note You need to log in before you can comment on or make changes to this bug.