Bug #27690: When provisioning a RHEL 8 with network bond, the system is provisioned but all network interfaces are down - Foreman

Actions

Copy link

Bug #27690

closed

When provisioning a RHEL 8 with network bond, the system is provisioned but all network interfaces are down

Added by Lukas Zapletal about 5 years ago. Updated about 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Templates

Target version:

Difficulty:

Triaged:

Yes

Bugzilla link:

1739878

Pull request:

https://github.com/theforeman/community-templates/pull/609

Fixed in Releases:

1.24.0

Found in Releases:

Red Hat JIRA:

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.

Actions

Copy link

Updated by Lukas Zapletal about 5 years ago

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.
Triaged changed from No to Yes
Pull request https://github.com/theforeman/community-templates/pull/609 added

Actions

Copy link

Updated by Lukas Zapletal about 5 years ago

Project changed from Templates to Foreman
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
Category set to Templates
Status changed from New to Resolved