Bug 1004885
| Summary: | LVM's UUID on PV not recognized | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gene Czarcinski <gczarcinski> | ||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 19 | CC: | anaconda-maint-list, dshea, gczarcinski, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | anaconda-20.17-1.fc20 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | |||||||||||||
| : | 1008048 (view as bug list) | Environment: | |||||||||||
| Last Closed: | 2013-09-19 02:41:03 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: | 1008048 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Gene Czarcinski
2013-09-05 16:39:32 UTC
Please include the relevant portion of your ks.cfg along with the logs (esp. storage.log and anaconda.log) from a failed attempt at using said ks.cfg. Thanks. To keep things simple, I created a KVM virtual for testing. I started with two disks and installed. I then reinstalled keeping the partitions but specifying the specific partitions. Naturally, those installations worked fine. Then, I changed all of the --onpart=vd_ specifications to --onpart=UUID=_ specifications and as expected, anaconda had a problem. The kickstart fragment is below and the attachments follow. ---------------------------------------------------------- # Partitions ignoredisk --only-use=vda,vdb #clearpart --all --initlabel --drives=vda,vdb clearpart --none #++1++ #part /boot --ondisk=vda --asprimary --size=500 --fstype=ext4 #part swap --ondisk=vda --asprimary --size=2048 #++2++ #part /boot --fstype=ext4 --onpart=vda1 #part swap --noformat --onpart=vda2 #++3++ part /boot --fstype=ext4 --onpart=UUID=71bc3228-1ccc-408c-b485-024b16e87d6d part swap --noformat --onpart=UUID=30582124-ad5f-45a4-8e5d-ac857b66ed94 #++1++ #part pv.01 --ondisk=vda --asprimary --size=500 --grow #volgroup VGa --pesize=32768 pv.01 #logvol / --fstype=ext4 --name=root --vgname=VGa --size=1000 --grow #++2++ #part pv.01 --noformat --onpart=vda3 #++3++ part pv.01 --noformat --onpart=UUID=ZVMWsc-FbZV-t3QL-IegT-maR0-jIex-EUmRzo volgroup VGa --noformat pv.01 logvol / --fstype=ext4 --name=root --vgname=VGa --useexisting #++1++ #part pv.02 --ondisk=vdb --asprimary --size=500 --grow #volgroup VGb --pesize=32768 pv.02 #logvol /home --fstype=ext4 --name=home --vgname=VGb --size=7680 --grow #++2++ #part pv.02 --noformat --onpart=vdb1 #++3++ part pv.02 --noformat --onpart=UUID=CCRxVn-QMH1-WeAZ-AVeP-W0xI-fD09-yxR1hk volgroup VGb --noformat pv.02 logvol /home --fstype=ext4 --name=home --vgname=VGb --noformat Created attachment 794929 [details]
anaconda.log
Created attachment 794930 [details]
storage.log
Created attachment 794931 [details]
output of blkid
What is the error message you got? Can you attach /tmp/anaconda-tb-* to this report? You can disregard my last request for information. I have a potential fix, which you can test by appending the following to the boot command line: inst.updates=http://dlehman.fedorapeople.org/updates/updates-1004885.0.img Let me know how it goes. Thanks. I am glag I have this set up in a KVM virtual so that it is easy to test. Unfortunately, with or without specifying a kickstart file, specifying this update causes anaconda to crash almost immediately. I am attaching a screenshot with the traceback messages. Created attachment 795111 [details]
traceback from running updates-1004885.0.img
Sorry about that -- I forgot you were using F19 (as opposed to rawhide/F20). Here is an updates image URL that should be compatible with your version of anaconda: inst.updates=http://dlehman.fedorapeople.org/updates/updates-1004885.1.img (note the '.1' as opposed to the '.0' from the previous URL) +1 Good work! That did the trick! About the only other thing is that this: http://fedoraproject.org/wiki/Anaconda/Kickstart probably needs to be updated to specifically state that the "special" LVM UUID on a PV can be used. I set up a F20/rawhide test too. anaconda-20.13-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.13-1.fc20 Package anaconda-20.13-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-20.13-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16296/anaconda-20.13-1.fc20 then log in and leave karma (feedback). anaconda-20.14-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.14-1.fc20 anaconda-20.15-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.15-1.fc20 anaconda-20.16-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.16-1.fc20 anaconda-20.17-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.17-1.fc20 anaconda-20.17-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |