Bug #27690
When provisioning a RHEL 8 with network bond, the system is provisioned but all network interfaces are down
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Templates
Target version:
-
Fixed in Releases:
Found in Releases:
Description
This is due to the configuration NM_CONTROLLED=no added to all interfaces by the network configuration snippets, like in the example below:
[root@levi-ribron network-scripts]# cat ifcfg-ens3 BOOTPROTO="none" DEVICE=ens3 HWADDR="52:54:00:0b:25:1b" ONBOOT=yes PEERDNS=no PEERROUTES=no DEFROUTE=no NM_CONTROLLED=no MASTER=bond0 SLAVE=yes
As in RHEL 8 legacy network scripts are not installed by default, all the interfaces with NM_CONTROLLED=no won't be initialized.
Associated revisions
History
#1
Updated by Lukas Zapletal almost 3 years ago
- Triaged changed from No to Yes
- Subject changed from When provisioning a RHEL 8 with network bond, the system is provisioned but all network interfaces are down after the installation reboots. to When provisioning a RHEL 8 with network bond, the system is provisioned but all network interfaces are down after the installation reboots.
- Pull request https://github.com/theforeman/community-templates/pull/609 added
#2
Updated by Lukas Zapletal almost 3 years ago
- Status changed from New to Resolved
- Category set to Templates
- Subject changed from When provisioning a RHEL 8 with network bond, the system is provisioned but all network interfaces are down after the installation reboots. to When provisioning a RHEL 8 with network bond, the system is provisioned but all network interfaces are down
- Project changed from Templates to Foreman
#3
Updated by Rahul Bajaj almost 3 years ago
- Status changed from Resolved to Closed
#4
Updated by Ewoud Kohl van Wijngaarden almost 3 years ago
- Fixed in Releases 1.24.0 added
Fixes #27690 - don't add NM_CONTROLLED