Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1573790

Summary: [RFE] A command to run metadata cleaning on ironic nodes
Product: Red Hat OpenStack Reporter: Dmitry Tantsur <dtantsur>
Component: python-tripleoclientAssignee: Dmitry Tantsur <dtantsur>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14.0 (Rocky)CC: dsneddon, hbrock, jslagle, mburns, racedoro, sasha
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-10.2.1-0.20180709114814.e5ce9a8.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:49:38 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 Dmitry Tantsur 2018-05-02 09:41:39 UTC
Since we cannot agree on re-enabling automated cleaning in the undercloud (see bug 1437142), we should at least provide a simple way to clean nodes via CLI/GUI. This RFE suggests creating a workflow and a tripleoclient command to invoke it.

Comment 1 Dmitry Tantsur 2018-05-02 09:46:10 UTC
Ramon, Dan,

Could you please consider putting this RFE on your radar instead of https://bugzilla.redhat.com/show_bug.cgi?id=1437142?

Comment 8 Alexander Chuzhoy 2018-10-03 17:36:23 UTC
Verified:
Environment:
python-tripleoclient-10.5.1-0.20180906012842.el7ost.noarch


It's possible to clean metadata with:
openstack overcloud node clean <node uuid>  #for single node

openstack overcloud node clean --all-manageable # for all manageable nodes

Comment 10 errata-xmlrpc 2019-01-11 11:49:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045