Bug #31631
Booting to anaconda with bond configured run into timeout
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Templates
Target version:
-
Pull request:
Found in Releases:
Description
If we try to install a CentOS box via network (iPXE -> dracut -> anaconda) the boot process run into timeout.
The bond will be configured full functional in dracut and there the kickstart file can be loaded but starting anaconda run into timeout.
Test to boot with PXE only with a single nic doesn't solve the problem at all. So we are able to start anaconda but installation won't start because of unconfigured network.
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot 6 months ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8259 added
#2
Updated by The Foreman Bot 6 months ago
- Fixed in Releases 2.4.0 added
#3
Updated by Christian Meißner 6 months ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset foreman|25dfbb3830a58878e032868d862ea90116597353.
#4
Updated by Tomer Brisker 4 months ago
Updated by - Category set to Templates
#5
Updated by Tomer Brisker 3 months ago
- Fixed in Releases 2.3.4 added
#6
Updated by Lukas Zapletal 3 months ago
Updated by - Related to Bug #31625: Puppet Environments are not listed properly in the SCP details page added
#7
Updated by Tomer Brisker 3 months ago
- Related to deleted (Bug #31625: Puppet Environments are not listed properly in the SCP details page)
#8
Updated by Tomer Brisker 3 months ago
- Related to Bug #31626: bondslaves in kickstart kernel options should be string not list added
#9
Updated by Lukas Zapletal 3 months ago
- Bugzilla link set to 1935088
fixes #31631 - configure bond the right way
The definition of a bond was wrong. We now generate a device with the
give name from foreman.
We also fix the bond slave list generation (related to #31626).