Project

General

Profile

Bug #31631

Booting to anaconda with bond configured run into timeout

Added by Christian Meißner 3 months ago. Updated 1 day ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Templates
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
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.

Associated revisions

Revision 25dfbb38 (diff)
Added by Christian Meißner 3 months ago

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).

History

#1 Updated by The Foreman Bot 3 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/8259 added

#2 Updated by The Foreman Bot 3 months ago

  • Fixed in Releases 2.4.0 added

#3 Updated by Christian Meißner 3 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Tomer Brisker about 1 month ago

  • Category set to Templates

#5 Updated by Tomer Brisker 1 day ago

  • Fixed in Releases 2.3.4 added

Also available in: Atom PDF