Bug 806931
| Summary: | "network --device link --activate" in kickstart inside initrd.img breaks anaconda | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, robatino, satellitgo, vanmeeuwen+fedora, wwoods | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | RejectedBlocker | ||||||
| Fixed In Version: | anaconda-17.16-1.fc17 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-05-03 18:25:28 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: | 752653 | ||||||
| Attachments: |
|
||||||
|
Description
Kamil Páral
2012-03-26 14:29:46 UTC
Marking as F17 Beta blocker: "The installer must be able to use all kickstart delivery methods" https://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria Please note this line: [ 3.739702] dracut Warning: 'method=' is deprecated. Using 'repo=http://download.fedoraproject.org/pub/fedora/linux/development/17/i386/os/' instead. That means dracut knows where to find the root image. It just doesn't download it for some reason. dracut:/# cat /proc/cmdline method=http://download.fedoraproject.org/pub/fedora/linux/development/17/i386/os/ console=ttyS0 ks=file:/ks.cfg rd.debug I reproduced this with manually created initrd.img. I added ks.cfg file and then booted from kernel pair in VM. I used these kernel options: method=http://download.fedoraproject.org/pub/fedora/linux/development/17/i386/os/ ks=file:/ks.cfg It behaves the same as described above. If I remove the "ks=" option it behaves correctly - it downloads the root image. I reproduced this with manually created initrd.img. I added ks.cfg file and then booted from kernel pair in VM. I used these kernel options: method=http://download.fedoraproject.org/pub/fedora/linux/development/17/i386/os/ ks=file:/ks.cfg It behaves the same as described above. If I remove the "ks=" option it behaves correctly - it downloads the root image. Discussed at 2012-03-26 QA meeting acting as a blocker review meeting. Accepted as a blocker per criterion "The installer must be able to use all kickstart delivery methods". -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Could you attach the ks.cfg you are using? Created attachment 573018 [details]
kickstart I used
anaconda-17.15-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.15-1.fc17 Package anaconda-17.15-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.15-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4745/anaconda-17.15-1.fc17 then log in and leave karma (feedback). anaconda-17.16-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.16-1.fc17 anaconda-17.16-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. This is not fixed with F17 Beta RC2. If I remove this line from the kickstart it works: network --device link --activate If I leave it there, it breaks. does the ks work when sourced any other way, if it has that line in it? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Good call. It works OK with ks=http and ks=nfs. I didn't try other methods. Discussed at the 2012-03-30 blocker review meeting. As the kickstart sourcing now works (as of RC2), and this is now a different problem with specific kickstart contents, we agreed this no longer constitutes a blocker and should be dropped to NTH. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Anaconda maintainers, please note, however, that we would really love to see this fixed, because our automated test suite currently uses exactly that kickstart and it's the reason why it doesn't get past boot... http://autoqa.fedoraproject.org/resultsdb/frontend/search?type=Testcase&terms=rats_install Thanks. Proposing as Final blocker. We don't seem to have criteria saying a kickstart with valid contents must work. Discussed at 2012-04-20 blocker review meeting - http://meetbot.fedoraproject.org/fedora-bugzappers/2012-04-20/fedora-bugzappers.2012-04-20-17.01.log.txt . Rejected as a blocker for now as we indeed do not cover this in the criteria, but could be re-proposed if a criterion is added. It seems difficult to formulate such a criterion, however. Does this still fail with F17 Beta? It seems to be working here.. It really is fixed in F17 Beta GOLD! Thanks. Reopening, this is broken again. I used daily F17 development compose and when using the same kickstart it breaks again: [ 5.924950] dracut Warning: 'method=' is deprecated. Using 'repo=http://dl.fedoraproject.org/pub/fedora/linux/development/17/i386/os/' instead. dracut Warning: 'method=' is deprecated. Using 'repo=http://dl.fedoraproject.org/pub/fedora/linux/development/17/i386/os/' instead. [ 5.941403] dracut: anaconda: parsing kickstart /fedora.ks [ 6.602987] dracut: rd.luks=0: removing cryptoluks activation [ 6.623960] dracut: rd.lvm=0: removing LVM activation [ 6.656924] dracut: FATAL: Please supply bootdev argument for multiple ip= lines [ 6.659117] dracut: Refusing to continue [ 6.661050] dracut Warning: Signal caught! dracut Warning: Signal caught! [ 6.663333] dracut Warning: dracut: FATAL: Please supply bootdev argument for multiple ip= lines dracut Warning: dracut: FATAL: Please supply bootdev argument for multiple ip= lines [ 6.667672] dracut Warning: dracut: Refusing to continue dracut Warning: dracut: Refusing to continue [ 6.670366] dracut Warning: /dev/root does not exist dracut Warning: /dev/root does not exist [ 6.673621] Kernel panic - not syncing: Attempted to kill init! [ 6.675277] Pid: 1, comm: init Not tainted 3.3.4-1.fc17.i686 #1 [ 6.676947] Call Trace: [ 6.677718] [<c09201d8>] ? printk+0x2d/0x2f [ 6.678918] [<c09200b4>] panic+0x81/0x178 [ 6.680182] [<c043b51f>] do_exit+0x7ff/0x800 [ 6.681443] [<c043b7b4>] do_group_exit+0x34/0xa0 [ 6.682763] [<c043b838>] sys_exit_group+0x18/0x20 [ 6.684102] [<c0928074>] syscall_call+0x7/0xb My command line: $ virt-install --name AutoQA --ram 1024 --vcpus 1 --os-type linux --os-variant fedora15 --disk path=/var/lib/libvirt/images/AutoQA.img,size=10 --location http://dl.fedoraproject.org/pub/fedora/linux/development/17/i386/os/ --graphics none --initrd-inject=/usr/share/autotest/tests/rats_install/fedora.ks --extra-args "sshd serial console=ttyS0 ks=file:/fedora.ks" Proposing as NTH. A lot of existing kickstarts may be broken and we can't fix this with an update after final release. I'm 98% sure this is caused by a bug in dracut, which should be fixed by this patch: http://article.gmane.org/gmane.linux.kernel.initramfs/2639 * Using a kickstart with "network --device=link" causes parse-kickstart to write "ip=..." args to /etc/cmdline.d, then unset CMDLINE * The bug with _getcmdline causes the "ip=..." arg to get duplicated * "getargs ip=" returns the duplicated "ip=..." args, and then the network module dies with the "Please supply bootdev argument for multiple ip= lines" error. Please file a new bug against dracut, since this is a totally different problem than the original one in this bug. OK, thanks, reported as bug 818707. |