Description of problem:
RHEL 9 provisioned via satellite, NetworkManager creates two network connections. "System ens192" and an extra unused "ens192"
Version-Release number of selected component (if applicable):
Satellite version 6.12
How reproducible:
100%
Steps to Reproduce:
1. Deploy a Rhel-9 host from the satellite.
2. Host provisioned successfully, however, NetworkManager create two network connections. "System ens192" and an extra unused "ens192"
Actual results:
# nmcli con show
NAME UUID TYPE DEVICE
System ens32 152beb06-47c5-c5e8-95a9-385590654382 ethernet ens32
ens32 8e747bfa-c416-4018-9718-3932492ce092 ethernet --
Expected results:
The name for the active interface should be ens32 and NetworkManager should update the uuid with the correct name.
Additional info:
cat /etc/NetworkManager/system-connections/ens32.nmconnection
[connection]
id=ens32
uuid=8e747bfa-c416-4018-9718-3932492ce092
type=ethernet
interface-name=ens32
[ethernet]
mtu=1500
[ipv4]
dns=xx.xx.xx.xx;xx.xx.x.x;
method=auto
[ipv6]
addr-gen-mode=eui64
method=ignore
[proxy]
===============================================================
cat /etc/sysconfig/network-scripts/ifcfg-ens32
BOOTPROTO="dhcp"
DOMAIN="example.com"
DEVICE=ens32
HWADDR="00:50:56:b4:1e:c4"
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
DEFROUTE=yes
MTU=1500
Hi,
I suggest to remove the BZ from the 6.13 scope, this issue is there for some time (from RHEL 7),
and implementing correct network configuration which is backwards compatible back to RHEL 6 is just not feasible in the 6.13 scope.
Comment 4Pablo Fernández Rodríguez
2023-10-30 14:19:19 UTC
Customer on case 03647169 using satellite-6.13.3-1.el8sat.noarch is also hitting this bug