Bug 1380646

Summary: [RFE] The default scheme of "Manual partitioning" should use "LVM Thin Provisioning"
Product: [oVirt] ovirt-node Reporter: cshao <cshao>
Component: Installation & UpdateAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED DUPLICATE QA Contact: Qin Yuan <qiyuan>
Severity: medium Docs Contact:
Priority: high    
Version: 4.0CC: bugs, dguo, fdeutsch, huzhao, jbenedic, jiawu, leiwang, rbarry, weiwang, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.2.0Keywords: FutureFeature
Target Release: ---Flags: fdeutsch: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack?
cshao: testing_ack+
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: 2017-01-05 14:53:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1380767    
Bug Blocks:    
Attachments:
Description Flags
scheme-lvm-tp
none
/var/log; /tmp none

Description cshao 2016-09-30 09:00:41 UTC
Created attachment 1206180 [details]
scheme-lvm-tp

Description of problem:
"LVM Thin Provisioning" scheme have been used for auto partition.
The default scheme of "Manual partitioning" should use "LVM Thin Provisioning"

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20160928.0
imgbased-0.8.5-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Anaconda interactive install RHVH.
2. Choose manual partition.
3. Focus on the pop-up partition scheme.

Actual results:
The default scheme of "Manual partitioning" is "LVM"

Expected results:
The default scheme of "Manual partitioning" should use "LVM Thin Provisioning"

Additional info:

Comment 1 cshao 2016-09-30 09:02:05 UTC
Created attachment 1206182 [details]
/var/log; /tmp

Comment 2 Red Hat Bugzilla Rules Engine 2016-09-30 09:28:55 UTC
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 3 Ryan Barry 2016-09-30 14:09:13 UTC
This is not something which is currently able to be set without forking Anaconda.

I filed an RFE against platform which would allow us to set this value through the installclass, but we'll be blocked from fixing this until that's resolved.

Comment 4 Fabian Deutsch 2016-10-20 07:02:42 UTC
*** Bug 1379138 has been marked as a duplicate of this bug. ***

Comment 5 Fabian Deutsch 2016-12-06 09:25:09 UTC
*** Bug 1394661 has been marked as a duplicate of this bug. ***

Comment 6 Fabian Deutsch 2017-01-05 14:53:31 UTC

*** This bug has been marked as a duplicate of bug 1374007 ***