Bug 1303974

Summary: [Docs][Install][RFE] Wipe After Delete option can now be set in engine-setup
Product: Red Hat Enterprise Virtualization Manager Reporter: Paul Dwyer <pdwyer>
Component: DocumentationAssignee: Byron Gravenorst <bgraveno>
Status: CLOSED CURRENTRELEASE QA Contact: Megan Lewis <melewis>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.0CC: amureini, gklein, ishaby, lbopf, lsurette, pdwyer, rbalakri, yeylon, ylavi
Target Milestone: ovirt-3.6.3Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-11 03:44:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1161219    
Bug Blocks:    

Description Paul Dwyer 2016-02-02 15:15:16 UTC 
Description of problem:
Wipe after Delete option is configurable in rhevm-setup for RHEV3.6 as per bz 1161219

Checking the RHEV3.6 beta documentation, this option is not mentioned in the install guide at
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6-Beta/html/Installation_Guide/index.html

Can we get this added before GA?

Version-Release number of selected component (if applicable):
RHEV3.6

How reproducible:
install guide at
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6-Beta/html/Installation_Guide/index.html


Additional info:
rhevm-setup now asks
"Default SAN wipe after delete (Yes,No) [No]:"
Comment 1 Lucy Bopf 2016-02-08 00:04:34 UTC 
Thanks, Paul, for reporting this feature.

Updating description, and assigning to Byron for review.
Comment 3 Idan Shaby 2016-02-14 08:17:20 UTC 
Sounds like a bug to me. So no, that doesn't mean that you will need to rerun engine-config every time.
The engine-setup just "recalls" the last input it got from the user and prints it out to the CONFIGURATION PREVIEW section.
You can either set it to true on the first setup, or you can set it to true via engine-config. Either way, the engine-setup will show the last input it got from the user, and not the up to date value.