-
Bug
-
Resolution: Done
-
Undefined
-
None
-
rhos-18.0.z
-
None
-
0
-
False
-
-
False
-
?
-
None
-
-
-
-
Critical
During BMH provisioning phase, the bonds have to be configured in mode 802.3ad but for some reason after cloud-init process the bonds are configured in mode round-robin. Because of that there is no connectivity by ctlplane network.
After bond mode is modified manually to 802.3ad, connectivity goes up.
The question is why is not taking the correct bond mode config? and how to fix it?
network data secret for that compute:
# networkData links: - name: ens15f2 id: ens15f2 type: phy ethernet_mac_address: "xxx" - name: ens8f1 id: ens8f1 type: phy ethernet_mac_address: "xxx" - name: ens3f0 id: ens3f0 type: phy ethernet_mac_address: "xxx" - name: ens15f1 id: ens15f1 type: phy ethernet_mac_address: "xxx" - name: bond0 id: bond0 type: bond bond_mode: 802.3ad bond_links: - ens15f2 - ens8f1 - name: bond1 id: bond1 type: bond bond_mode: 802.3ad bond_links: - ens3f0 - ens15f1 networks: - link: bond0 id: bond0 type: ipv4 ip_address: xxx netmask: "255.255.255.0" routes: - network: 0.0.0.0 netmask: 0.0.0.0 gateway: xxx - link: bond1 id: bond1 type: ipv4 ip_address: xxx netmask: "255.255.255.0" routes: - network: xxx netmask: 255.255.255.128 gateway: xxx - network: xxx netmask: 255.255.255.128 gateway: xxx - network: xxx netmask: xxx gateway: xxx - network: xxx netmask: xxx gateway: xxx services: - type: dns-nameserver address: - xxx search: - ctlplane.osp.lab.example
Riproduced in: FR4
