Bug 1340240
| Summary: | reqpart leads to traceback | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Fabian Deutsch <fdeutsch> | ||||
| Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.2 | CC: | cshao, dguo, fdeutsch, huzhao, jreznik, leiwang, mhruscak, weiwang, yaniwang, ycui | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 7.3 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | anaconda-21.48.22.77-1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-08-07 15:48:58 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1329957 | ||||||
| Attachments: |
|
||||||
Urgent, because we need this for RHEV-H Next, and we need to support both, bios and uefi systems. One note: When the ks is complete and can trigger an auto-install. Then no traceback is raised, I am unable to reproduce this with the current 7.3 nightly. Can you post a complete kickstart that exhibits the problem? 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. 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. I'll try to come up with the exact steps to reproduce this. 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. 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. Reproducer steps can be found in comment 8. edit: comment #8 step 3: use kickstart in description, add needed lines except e.g. timezone setting |
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: