Bug 892669
| Summary: | slow NIC and local kickstart -> anaconda crash | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 18 | CC: | awilliam, cakersq, g.kaviyarasu, jonathan, robatino, sbueno, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | Keywords: | CommonBugs | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | AcceptedNTH RejectedBlocker https://fedoraproject.org/wiki/Common_F18_bugs#netinst-kickstart | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-02-05 14:31:31 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: | 752665 | ||||||||
| Attachments: |
|
||||||||
|
Description
Kamil Páral
2013-01-07 14:58:34 UTC
Created attachment 674102 [details]
anaconda-tb-aokiSR
Created attachment 674105 [details]
additional exceptions from tty1 (not in logs)
We might argue this violates: " The installer must be able to use all supported local and remote package source options " https://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria or some other critera. Let's discuss. I don't think this is a widespread enough case to warrant being a F18 blocker. Discussed at 2013-01-07 QA meeting acting as a blocker review meeting: http://meetbot.fedoraproject.org/fedora-meeting/2013-01-07/fedora-qa.2013-01-07-16.01.log.txt . Agreed that local kickstart / remote packages / slow network is too much of a corner case combination to block release. Obvious workaround - and a much more likely use case - is to host the kickstart remotely (it's quite unusual to have a really *local* kickstart). Accepted as NTH, though, as it is at least theoretically an install-breaker, and document if we don't fix it. I also ran into this problem, though with a different error message, when using a self contained CD with packages and kickstart to deploy. The error I got was "cannot load file:///tmp/anaconda-yum.conf". As a quick work around, you can place "nmcli nm enable false" in your kickstart %pre section. This will disable the unnecessary NetworkManager and nm-online processes, and allow the Anaconda systemd unit file to create the anaconda-yum.conf and yum.repos.d. Usually first thing I do in Fedora is disable NetworkManager, firewalld, and other unnecessary control daemons. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |