Bug 1412351

Summary: [RFE] [Ironic] Need to have a way to check the progress of a cleaning process. May take a very long time.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: openstack-ironicAssignee: OSP Team <rhos-maint>
Status: CLOSED DEFERRED QA Contact: mlammon
Severity: unspecified Docs Contact:
Priority: low    
Version: 12.0 (Pike)CC: dtantsur, jkreger, mburns, mlammon, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-20 21:34:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.
Comment 2 Julia Kreger 2021-07-20 21:34:55 UTC 
Marking Deferred as I do not believe the team will take this item up at this time. If requirements are otherwise, please let us know.