Bug 1398657

Summary: [RFE] Re-enable node cleaning in undercloud
Product: Red Hat OpenStack Reporter: Dmitry Tantsur <dtantsur>
Component: instack-undercloudAssignee: Dmitry Tantsur <dtantsur>
Status: CLOSED ERRATA QA Contact: mlammon
Severity: low Docs Contact:
Priority: low    
Version: 11.0 (Ocata)CC: achernet, dbecker, dsneddon, mburns, mlammon, morazi, nlevinki, racedoro, rbartal, rhel-osp-director-maint, sclewis
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: instack-undercloud-6.0.0-0.20170220135156.d695df8.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-17 19:47:52 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:
Bug Depends On:    
Bug Blocks: 1421830    

Description Dmitry Tantsur 2016-11-25 13:47:22 UTC 
We've disabled cleaning because it takes time and may be surprising for users. However, we need to at least provide a way to enable it back, as not wiping disks causes problems like https://bugzilla.redhat.com/show_bug.cgi?id=1244056 (and a few more).

Upstream blueprint: https://blueprints.launchpad.net/tripleo/+spec/re-enable-cleaning
Comment 1 Dmitry Tantsur 2016-11-25 13:50:15 UTC 
*** Bug 1244056 has been marked as a duplicate of this bug. ***
Comment 2 Dmitry Tantsur 2017-01-06 16:23:51 UTC 
This landed with a slightly modified scope: cleaning now works out-of-box, if enabled by setting "clean_nodes = True" in undercloud.conf. We need a separate RFE if we want it by default.
Comment 8 errata-xmlrpc 2017-05-17 19:47:52 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-2017:1245