Bug 1380646 - [RFE] The default scheme of "Manual partitioning" should use "LVM Thin Provisioning"
Summary: [RFE] The default scheme of "Manual partitioning" should use "LVM Thin Provis...
Keywords:
Status: CLOSED DUPLICATE of bug 1374007
Alias: None
Product: ovirt-node
Classification: oVirt
Component: Installation & Update
Version: 4.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Fabian Deutsch
QA Contact: Qin Yuan
URL:
Whiteboard:
: 1379138 1394661 (view as bug list)
Depends On: 1380767
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-30 09:00 UTC by cshao
Modified: 2017-01-05 14:53 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-05 14:53:31 UTC
oVirt Team: Node
Embargoed:
fdeutsch: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack?
cshao: testing_ack+

Attachments (Terms of Use)
scheme-lvm-tp (59.73 KB, image/png)
2016-09-30 09:00 UTC, cshao 		no flags Details
/var/log; /tmp (201.96 KB, application/x-gzip)
2016-09-30 09:02 UTC, cshao 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.