Bug 927315
Summary: | kickstart install stop at installation prompt, no disks selected | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> | ||||||||
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, g.kaviyarasu, jonathan, mattdm, mbanas, mkolman, rmarko, sbueno, vanmeeuwen+fedora | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | anaconda-19.21-1 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-04-30 04:39:23 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: | 920667 | ||||||||||
Attachments: |
|
Description
Orion Poplawski
2013-03-25 15:59:35 UTC
Created attachment 716082 [details]
storage.log
Created attachment 716085 [details]
anaconda.log
I can manually select vda for the install destination via the menu fine. *** Bug 927621 has been marked as a duplicate of this bug. *** The key here is that you have not specified an ignoredisk line, which is what the storage spokes are looking at to determine whether you've completed partitioning or not. Given that command is not required, we need to make the spokes smarter. What is the workaround in this case? Using ignoredisk doesn't seem to help. I've tried ignoredisk --drives=vda and ignoredisk --only-use=vda. Hi Chris, any update on this bug? This is currently blocking us from automated testing. Interesting that this only appears to happen on "vd" disks, not "sd". anaconda-19.21-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/anaconda-19.21-1.fc19 Package anaconda-19.21-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6338/anaconda-19.21-1.fc19 then log in and leave karma (feedback). Package anaconda-19.21-1.fc19, python-meh-0.23-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19 python-meh-0.23-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6338/python-meh-0.23-1.fc19,anaconda-19.21-1.fc19 then log in and leave karma (feedback). There is a workaround for this issue: it will work in graphics mode. So, simply remove the line "text" from your kickstart temporarily. anaconda-19.21-1.fc19, python-meh-0.23-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |