Actions
Bug #31631
closed
Booting to anaconda with bond configured run into timeout
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Templates
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
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.
Updated by The Foreman Bot almost 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8259 added
Updated by Christian Meißner almost 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|25dfbb3830a58878e032868d862ea90116597353.
Updated by Lukas Zapletal over 3 years ago
- Related to Bug #31625: Puppet Environments are not listed properly in the SCP details page added
Updated by Tomer Brisker over 3 years ago
- Related to deleted (Bug #31625: Puppet Environments are not listed properly in the SCP details page)
Updated by Tomer Brisker over 3 years ago
- Related to Bug #31626: bondslaves in kickstart kernel options should be string not list added
Actions