Bug 1762201
| Summary: | provisioning kickstart conflicts with static networking setup | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Dan Horák <dhorak> |
| Component: | general | Assignee: | beaker-dev-list |
| Status: | CLOSED WONTFIX | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | bpeck, cbouchar, jstodola |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-21 14:13:57 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: | 1761589 | ||
a sample of the provisioning kickstart - https://beaker.engineering.redhat.com/kickstart/6024063 |
Description of problem: The kickstart file used for provisioning machines always contains network --bootproto=dhcp --hostname=... command, which conflicts with the static networking setup used with s390x machines. I believe this became an issue after anaconda changed their network setup code to rely on NetworkManager. The "network" command shouldn't be used when the machine has network pre-configured from dracut/initrd environment, like our s390x guests. Version-Release number of selected component (if applicable): 26.5 as used at beaker.engineering.redhat.com How reproducible: 100% Steps to Reproduce: 1. run a reservesys job 2. select s390x 3. select Fedora30 4. supply ip= kernel option used by RHEL-8 Actual results: - traceback from /tmp/anamon with socket.gaierror: [Errno -2] Name or service not known - network connectivity lost in the "middle" of the provisioning process (right after the pre-install script finished) Expected results: - no traceback, machine accessible over network Additional info: "network --bootproto=dhcp" breaks installations with static networking setup outside beaker too The anamon crash isn't fatal, but the loss of network connectivity is.