Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1340240 - reqpart leads to traceback
Summary: reqpart leads to traceback
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 7.3
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-ng-platform
TreeView+ depends on / blocked
 
Reported: 2016-05-26 19:53 UTC by Fabian Deutsch
Modified: 2017-08-09 14:52 UTC (History)
10 users (show)

Fixed In Version: anaconda-21.48.22.77-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-07 15:48:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
traceback (508.53 KB, text/plain)
2016-05-26 19:53 UTC, Fabian Deutsch 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 58163 0 master ABANDONED ks: Drop reqpart for now 2016-06-09 19:37:09 UTC

Description Fabian Deutsch 2016-05-26 19:53:00 UTC 
Created attachment 1162268 [details]
traceback

Description of problem:
Using teh following kickstart leads to a traceback originating in reqpart:

clearpart --all --initlabel --disklabel=gpt
reqpart --add-boot
part pv.01 --size=42000 --grow
volgroup HostVG pv.01
logvol swap --vgname=HostVG --name=swap --fstype=swap --recommended
logvol none --vgname=HostVG --name=HostPool --thinpool --size=40000 --grow
logvol /    --vgname=HostVG --name=root --thin --poolname=HostPool --fsoptions="defaults,discard" --size=6000
logvol /var --vgname=HostVG --name=var --thin --poolname=HostPool --fsoptions="defaults,discard" --size=15000


Version-Release number of selected component (if applicable):
rhel 7.2

How reproducible:
Always

Steps to Reproduce:
1. rhel72 installer with this ks
2. Mni 64GB disk
3. enter storage spoke, hit "Done"

Traceback is raised.

Actual results:


Expected results:


Additional info:
Comment 1 Fabian Deutsch 2016-05-26 19:56:41 UTC 
Urgent, because we need this for RHEV-H Next, and we need to support both, bios and uefi systems.
Comment 2 Fabian Deutsch 2016-05-26 20:03:43 UTC 
One note: When the ks is complete and can trigger an auto-install. Then no traceback is raised,
Comment 3 Brian Lane 2016-05-27 19:08:23 UTC 
I am unable to reproduce this with the current 7.3 nightly. Can you post a complete kickstart that exhibits the problem?
Comment 4 Fabian Deutsch 2016-05-28 19:00:00 UTC 
Here you go:
https://gerrit.ovirt.org/gitweb?p=ovirt-node-ng.git;a=blob;f=data/ci-image-install.ks;h=2561be2ed2238a3b0499693b61ebfd76a177995d;hb=3890097eb8e9e33ded2990bd985c73747a15b388

It's a bit tricky to raise the tb in the UI:

I had to enter the storage spoke, select disks, ten hit Done - maybe something else.
Comment 5 Brian Lane 2016-06-01 00:15:53 UTC 
I still can't hit the TB, but something I found using different numbers than yours (I use 2x10GiB disks in my dedfault VMs) is that if 'part pv.01 --size=42000 --grow' is too big to coexist with reqpart it will fail by saying no disks selected. It isn't obvious what went wrong, even if you click the info bar in storage.
Comment 6 Fabian Deutsch 2016-06-01 13:43:09 UTC 
I'll try to come up with the exact steps to reproduce this.
Comment 7 Brian Lane 2016-06-01 21:00:17 UTC 
https://github.com/rhinstaller/anaconda/pull/655

would make it more clear that the actual problem isn't disk selection but that it is a problem with the kickstart's partitioning.
Comment 8 Marek Hruscak 2016-06-08 15:46:14 UTC 
I also hit this bug on RHEL-7.3-20160603.n.0 but in slightly various manner.
My steps to reproduce:

1. prepare KVM VM with 64G disk(I did not try smaller)
2. boot from boot.img
3. use kickstart from attachment
4. in Anaconda go to the Partitioning spoke
5. as manual configuration is selected by default in this case, hit Done to go to Blivet
6. you will see unpartitioned 64G space(img in attachment)
7.1 hit done, ignore warn msg, try to go to Blivet again
or
7.2 use rescan disks(notice warn msg) and then hit Done to go to Blivet again

As mentioned in comment #2 , this bug is possible to hit only if the kickstart is uncomplete(therefore commented timezone line in ks) and Partitioning spoke is visited - leaving partitioning as it is and just setting timezone and continue in installation will end without TB.
Comment 11 Fabian Deutsch 2016-07-20 16:10:49 UTC 
Reproducer steps can be found in comment 8.
Comment 13 Marek Hruscak 2016-07-21 17:23:21 UTC 
edit:
comment #8
step 3: use kickstart in description, add needed lines except e.g. timezone setting
Note You need to log in before you can comment on or make changes to this bug.