Bug 967527
Summary: | clearpart --none crashes anaconda if not enough space available | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vojtěch Boček <vbocek> | ||||||||||||||||||||||||||
Component: | anaconda | Assignee: | Chris Lumens <clumens> | ||||||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||||
Version: | 19 | CC: | ajsfedora, awilliam, dshea, g.kaviyarasu, jonathan, kparal, mkolman, robatino, sbueno, vanmeeuwen+fedora | ||||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||||
Whiteboard: | abrt_hash:53713078d0bfc18e26001752793a9cdbd3bc2ae5b051a966f3af1ce517e3aad6 AcceptedFreezeException RejectedBlocker | ||||||||||||||||||||||||||||
Fixed In Version: | pykickstart-1.99.32-1.fc19 | Doc Type: | Bug Fix | ||||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||||
Last Closed: | 2013-06-18 06:16:58 UTC | Type: | --- | ||||||||||||||||||||||||||
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: | 834091 | ||||||||||||||||||||||||||||
Attachments: |
|
Description
Vojtěch Boček
2013-05-27 11:03:11 UTC
Created attachment 753568 [details]
File: anaconda-tb
Created attachment 753569 [details]
File: anaconda.log
Created attachment 753570 [details]
File: backtrace
Created attachment 753571 [details]
File: environ
Created attachment 753572 [details]
File: ifcfg.log
Created attachment 753573 [details]
File: ks.cfg
Created attachment 753574 [details]
File: lsblk_output
Created attachment 753575 [details]
File: nmcli_dev_list
Created attachment 753576 [details]
File: packaging.log
Created attachment 753577 [details]
File: program.log
Created attachment 753578 [details]
File: storage.log
Created attachment 753579 [details]
File: syslog
Proposing as a Final blocker: "The installer must be able to complete a scripted installation which duplicates the default interactive installation as closely as possible. " http://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria#Scripted_installation This appears to be a race condition - it does not crash every time, I managed to reproduce it 3 out of 5 times. Also, pleas note that I forgot to "clearpart --none..." command in kickstart file to "clearpart --all...". After changing to --all, it no longer crashes, but disk setup is apparently bugged instead - it succeeds about 1 of 5 times, and fails at "No disks selected" the rest of the time. Discussed at 2013-05-29 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-29/f19final-blocker-review-1.2013-05-29-16.02.log.txt . We agreed to punt the decision on this one: we'd at least like to know i) does it crash with 'clearpart --none' and an empty disk, and ii) does it complete an install with 'clearpart --all' and an empty disk... Oh, but we accepted it as a freeze exception at least - at minimum it seems to merit that, crashers in fairly 'normal' kickstart runs are bad. >> i) does it crash with 'clearpart --none' and an empty disk No, but in 1 of 8 tries, the "Installation destination" section said "Automatic partitioning selected" instead of "No disks selected". >> ii) does it complete an install with 'clearpart --all' and an empty disk... No, results are the same as with --none: it stops with "No disks selected" most of the time, but at the fourth try it installed properly. We discussed this again at the meeting today. We still didn't come to a definite conclusion but there definitely appear to be worrying issues here. Kamil is going to split this bug into multiple bugs as the crash with clearpart --none and the failure to correctly configure storage with clearpart --all seem to be different issues. tflink and kparal were able to reproduce the failure to complete storage config properly sometimes with http://www.happyassassin.net/ks/967527.ks (based on the ks in the report), I wasn't: I did five tries and it worked each time. Let's use this bug for the original crash with clearpart --none. I moved the race condition with clearpart --all into bug 969327. Discussed at 2013-06-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-03/f19final-blocker-review-2.2013-06-03-16.00.log.txt . As the other case has been split off, this one is rejected as a blocker but accepted as a freeze exception issue. Outright crashes are bad and worth fixing, but we believe this one is hit only when using an invalid config: passing 'clearpart --none' when there is not sufficient free space for installation. Even if it didn't crash, the install wouldn't proceed until you entered some kind of valid disk configuration interactively - your kickstart configuration would not be used. So this doesn't seem to be blocker worthy. The 'workaround' is to actually use a valid configuration in your kickstart (either enough disk space available for install and 'clearpart --none', or specify some kind of space freeing operation). pykickstart-1.99.32-1.fc19,python-blivet-0.16-1.fc19,anaconda-19.30.6-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/pykickstart-1.99.32-1.fc19,python-blivet-0.16-1.fc19,anaconda-19.30.6-1.fc19 Package anaconda-19.30.7-1.fc19, pykickstart-1.99.32-1.fc19, python-blivet-0.16-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.30.7-1.fc19 pykickstart-1.99.32-1.fc19 python-blivet-0.16-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10913/pykickstart-1.99.32-1.fc19,python-blivet-0.16-1.fc19,anaconda-19.30.7-1.fc19 then log in and leave karma (feedback). pykickstart-1.99.32-1.fc19, python-blivet-0.16-1.fc19, anaconda-19.30.8-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. Verified fixed with F19 TC5 DVD. |