Bug 886647
| Summary: | Anaconda throws exception trying to setup network if non-existing network --device is specified in kickstart | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stuart Blackburn <stuart.blackburn> | ||||||||||||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 18 | CC: | awilliam, g.kaviyarasu, jonathan, pf.rhlists, robatino, rvykydal, sbueno, vanmeeuwen+fedora, vpodzime | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | AcceptedNTH RejectedBlocker | ||||||||||||||||||
| Fixed In Version: | anaconda-18.37.6-1 | Doc Type: | Bug Fix | ||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2013-01-02 21:48:34 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
Stuart Blackburn
2012-12-12 18:45:42 UTC
Created attachment 662560 [details]
install.log
I was asked to provide the anaconda.log, install.log and ifcfg.log. I have attached two of these. The ifcfg.log was empty, and therefore not attached. Throw this on the blocker list for discussion, though we'll need more detail on the exact problem here to evaluate it - anaconda team, if in looking at this you can identify the exact trigger conditions, that will help our evaluation. Thanks. (In reply to comment #2) > I was asked to provide the anaconda.log, install.log and ifcfg.log. I have > attached two of these. The ifcfg.log was empty, and therefore not attached. Thank you for the logs, but I was asking for /tmp/syslog, not install.log. Unfortunately this is the most valuable for us to discover why p3p2 does not have mac-address setting. Created attachment 663005 [details]
syslog from installation attempt on a VM with 2 NICs
Sorry, I missed this one initially. This is from a rerun of the install on the same VM. If you need anything else. Let me know.
(In reply to comment #5) > Created attachment 663005 [details] > syslog from installation attempt on a VM with 2 NICs > > Sorry, I missed this one initially. This is from a rerun of the install on > the same VM. If you need anything else. Let me know. Just a note -- please set the MIME type to text/plain next time. Bugzilla is unfortunately not smart enough to find out that you are attaching a text file if it doesn't have .txt extension. Discussed at 2012-12-17 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-17/f18final-blocker-review-5.2012-12-17-16.40.log.txt . Agreed we need more info to determine the status of this one. vpodzime, any idea what's causing this? If it helps, I created a new ISO with lorax today with the latest versions of FC18 RPMs except for rolling back the following: anaconda-18.29.2-1.fc18.x86_64.rpm anaconda-dracut-18.29.2-1.fc18.noarch.rpm anaconda-widgets-18.29.2-1.fc18.x86_64.rpm anaconda-yum-plugins-1.0-8.fc18.noarch.rpm NetworkManager-0.9.7.0-8.git20121004.fc18.x86_64.rpm NetworkManager-glib-0.9.7.0-8.git20121004.fc18.x86_64.rpm I was able to install successfully this new ISO on my VM and blade server with multiple NICs. The ISO I am having problems with contains the following versions: anaconda-18.37-1.fc18.x86_64 anaconda-dracut-18.37-1.fc18.x86_64 anaconda-yum-plugins-1.0-8.fc18.noarch anaconda-widgets-18.37-1.fc18.x86_64 NetworkManager-0.9.7.0-9.git20121004.fc18.x86_64 NetworkManager-glib-0.9.7.0-9.git20121004.fc18.x86_64 I have a patch that would fall back to behaviour of 18.29 for devices/connections with setting['802-3-ethernet']['mac-address'] not found (the yours). But I'd like to find out why the setting is missing for your device. I prepared updates image with - the fix mentioned above (so it should fix you issue) - dump of configuration to log files (so I could investigate why the setting is missing) could you please check this updates image (it is for F18 TC3) http://rvykydal.fedorapeople.org/updates.macaddress.img and attach /tmp/ifcfg.log, /tmp/syslog, /tmp/anaconda.log files? The updates image is used by adding updates=http://rvykydal.fedorapeople.org/updates.macaddress.img to boot options. Created attachment 665548 [details] anaconda.log from boot with updates.macaddress.img I am uploading new ifcfg.log, syslog and anaconda.log files from boot with kernel parameter updates=http://rvykydal.fedorapeople.org/updates.macaddress.img. I used my failing ISO image containing anaconda 18.37.1 because I do not know where/how to obtain the F18 TC3 ISO. The img seemed to fix the problem when installing on the VM with 2 NICs. Created attachment 665549 [details]
ifcfg.log from boot with updates.macaddress.img
Created attachment 665550 [details]
syslog from boot with updates.macaddress.img
Thanks for the logs, could you please post also kickstart file you are using: http://10.250.34.234/cblr/svc/op/ks/system/titenvm03 (I am intersted only in network commands from kickstart) Created attachment 665556 [details]
kickstart file
The root cause here is that dracut's module parse-kickstart is creating wrong ifcfg file for device eth0 (with missing HWADDR because such a device does not exist) based on this kickstart network command: network --device eth0 --bootproto dhcp whereas there are only devices p16p1 and p7p1 (eth1 and eth0 renamed by biosdevname in dracut) So you should either use "--device p7p1" or better specify the device with mac addres "--device 08:00:27:6D:82:7B" in your kickstart file. We might want to make parse-kickstart ignore non-existing devices instead of causing this mess with invalid ifcfg file. That would be more appropriate fix than the patch in updates image. I don't see this as F18 blocker, but I think I can make proper patch soon. Patch sent for review. That seems to fix it. We'll have to teach our PXE/cobbler server to insert the MAC address in the kickstart files. BTW, the eth0 reference in the kickstart file was a remanent from our last distro which was based on FC13. Sorry, we should have caught that ourselves. I guess it threw us off that the installation worked for the first couple of FC18 ISOs that we built. Based on the description in c#16 I'd be -1 blocker +1 NTH. +1 NTH by me. Pushed to master as commit 809943f673a874fd4332e40f0faa94301277d13b. Discussed at 2012-12-19 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-19/f18final-blocker-review-6.2012-12-19-17.02.log.txt . With the information from comment #16, we agree that this isn't really serious enough to merit blocker status, but is worth fixing, so it's rejected as a blocker, accepted as NTH. anaconda-18.37.6-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.37.6-1.fc18 Package anaconda-18.37.6-1.fc18, dracut-024-17.git20121220.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.37.6-1.fc18 dracut-024-17.git20121220.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20838/dracut-024-17.git20121220.fc18,anaconda-18.37.6-1.fc18 then log in and leave karma (feedback). Package dracut-024-17.git20121220.fc18, anaconda-18.37.8-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dracut-024-17.git20121220.fc18 anaconda-18.37.8-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20838/dracut-024-17.git20121220.fc18,anaconda-18.37.8-1.fc18 then log in and leave karma (feedback). dracut-024-17.git20121220.fc18, anaconda-18.37.8-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. Successfully tested a new ISO built with anaconda-18.37.8-1. Thank you so much for the fix! |