Bug 1139869
| Summary: | OS provisioning fails for em1 network device | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Balaji <bjayavel> | ||||||
| Component: | rhel-osp-installer | Assignee: | Marek Hulan <mhulan> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Omri Hochman <ohochman> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.0 (RHEL 7) | CC: | aberezin, bjayavel, lzap, mburns, mhulan, morazi, randy_perryman, rhos-maint, sseago, yeylon | ||||||
| Target Milestone: | z1 | Keywords: | Triaged, ZStream | ||||||
| Target Release: | Installer | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-09-17 11:22: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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Balaji
2014-09-09 21:02:14 UTC
I suspect that this is due to biosdevname being enabled on the discovery image and not the rest of the time. Can you try this: edit the /var/lib/tftpboot/pxelinux.cfg/default file add biosdevname=0 to the Append line save the file rediscover hosts and let me know if that fixes your issue? I've created a PR for this change upstream since it's a good change regardless. https://github.com/theforeman/foreman-installer-staypuft/pull/88 I set the value to biosdevname=0 in the /var/lib/tftpboot/pxelinux.cfg/default file, but the discovery fails. Created attachment 937087 [details]
Error on the target console during boot
Error on the console while provisioning.
biosdevname did not help in the end once we got around the failed discovery boot. Marek, Lukas, any ideas? Hey, as you can see from the screenshot, Foreman application returns 500 when trying to render the kickstart template. Can you paste Foreman logs here? This looks like some error in Foreman rather than Discovery. This will need some debugging of the provisioning template. I bet it will be in networking configuration part. Would it be possible to provide a foreman instance where we could test it? Just seeing foreman log might not help in this case. Created attachment 937618 [details]
updated screenshot of console with error
The kickstart error was a different issue and has been resolved. But the problem is persistent as shown in the updated screenshot. Can you check you installation images in /var/lib/tftpboot/boot for rhel7? Ideally paste their size and checksums. Also make sure the server has more than 1 GB of RAM. We do not support less then gig! The installer has 3GB and the target host has 48GB. Hence no concerns in that aspect. This might be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1141955 *** This bug has been marked as a duplicate of bug 1141955 *** |