Bug 1303974 - [Docs][Install][RFE] Wipe After Delete option can now be set in engine-setup
Summary: [Docs][Install][RFE] Wipe After Delete option can now be set in engine-setup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-3.6.3
: ---
Assignee: Byron Gravenorst
QA Contact: Megan Lewis
URL:
Whiteboard:
Depends On: 1161219
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-02 15:15 UTC by Paul Dwyer
Modified: 2016-03-11 03:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-11 03:44:19 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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