Bug 2089757 - [4.10.z backport] [BM][IPI] Installation with bonds fail - DaemonSet "openshift-ovn-kubernetes/ovnkube-node" rollout is not making progress
Summary: [4.10.z backport] [BM][IPI] Installation with bonds fail - DaemonSet "openshi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.10.z
Assignee: Jaime Caamaño Ruiz
QA Contact: Ross Brattain
URL:
Whiteboard:
: 2071574 (view as bug list)
Depends On: 2078866
Blocks: 2089763
TreeView+ depends on / blocked
 
Reported: 2022-05-24 11:27 UTC by Jaime Caamaño Ruiz
Modified: 2022-06-08 09:31 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2078866
: 2089763 (view as bug list)
Environment:
Last Closed: 2022-06-07 13:24:31 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 3159 0 None open [release-4.10] Bug 2089757: configure-ovs: avoid restarting NetworkManager 2022-05-28 01:00:38 UTC
Red Hat Product Errata RHBA-2022:4882 0 None None None 2022-06-07 13:24:51 UTC

Comment 5 Ross Brattain 2022-06-03 04:06:41 UTC 
Verified on 4.10.0-0.nightly-2022-06-02-013739  IPI baremetal dual-stack bonding 


Verified using `autoconnect-priority=99` as per bug 2055433, comment 1


## /etc/NetworkManager/system-connections/bond0.nmconnection

[connection]
id=bond0
type=bond
interface-name=bond0
autoconnect=true
connection.autoconnect-slaves=1
autoconnect-priority=99

[bond]
mode=802.3ad
miimon=100

[ipv4]
method=auto
dhcp-timeout=2147483647

[ipv6]
method=auto
dhcp-timeout=2147483647


## /etc/NetworkManager/system-connections/enp5s0.nmconnection

[connection]
id=enp5s0
type=ethernet
interface-name=enp5s0
master=bond0
slave-type=bond
autoconnect=true
autoconnect-priority=99## /etc/NetworkManager/system-connections/enp5s0-slave-ovs-clone.nmconnection

[connection]
id=enp5s0-slave-ovs-clone
uuid=f72e0264-a9ed-4b4f-93d7-4eafcf8c8abd
type=ethernet
autoconnect-priority=100
interface-name=enp5s0
master=7495a9b4-4b99-42e1-8836-f556f576404d
permissions=
slave-type=bond
timestamp=1654228357

[ethernet]
mac-address-blacklist=

## /etc/NetworkManager/system-connections/enp6s0.nmconnection

[connection]
id=enp6s0
type=ethernet
interface-name=enp6s0
master=bond0
slave-type=bond
autoconnect=true
autoconnect-priority=99

## /etc/NetworkManager/system-connections/enp6s0-slave-ovs-clone.nmconnection

[connection]
id=enp6s0-slave-ovs-clone
uuid=e6cd315d-20c9-4750-b55a-f338ac4dc58f
type=ethernet
autoconnect-priority=100
interface-name=enp6s0
master=7495a9b4-4b99-42e1-8836-f556f576404d
permissions=
slave-type=bond
timestamp=1654228353

[ethernet]
mac-address-blacklist=




Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + for connection in $(nmcli -g NAME c | grep -- "$MANAGED_NM_CONN_SUFFIX")
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + activate_nm_conn enp6s0-slave-ovs-clone
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + local conn=enp6s0-slave-ovs-clone
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: ++ nmcli -g GENERAL.STATE conn show enp6s0-slave-ovs-clone
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + local active_state=activated
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + '[' activated '!=' activated ']'
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + echo 'Connection enp6s0-slave-ovs-clone already activated'
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: Connection enp6s0-slave-ovs-clone already activated
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + nmcli c mod enp6s0-slave-ovs-clone connection.autoconnect yes
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + activate_nm_conn ovs-if-phys0
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + local conn=ovs-if-phys0
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: ++ nmcli -g GENERAL.STATE conn show ovs-if-phys0
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + local active_state=activated
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + '[' activated '!=' activated ']'
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + echo 'Connection ovs-if-phys0 already activated'
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: Connection ovs-if-phys0 already activated
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + nmcli c mod ovs-if-phys0 connection.autoconnect yes
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + activate_nm_conn ovs-if-br-ex
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + local conn=ovs-if-br-ex
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: ++ nmcli -g GENERAL.STATE conn show ovs-if-br-ex
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + local active_state=
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + '[' '' '!=' activated ']'
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + for i in {1..10}
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + echo 'Attempt 1 to bring up connection ovs-if-br-ex'
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: Attempt 1 to bring up connection ovs-if-br-ex
Jun 03 03:09:18 master-0-2 configure-ovs.sh[1971]: + nmcli conn up ovs-if-br-ex
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/12)
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + s=0
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + break
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + '[' 0 -eq 0 ']'
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + echo 'Brought up connection ovs-if-br-ex successfully'
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: Brought up connection ovs-if-br-ex successfully
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + nmcli c mod ovs-if-br-ex connection.autoconnect yes
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + '[' -f /etc/ovnk/extra_bridge ']'
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + handle_exit
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + e=0
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + '[' 0 -eq 0 ']'



Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + ip route show
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: default via 192.168.123.1 dev br-ex proto dhcp metric 48
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: 192.168.123.0/24 dev br-ex proto kernel scope link src 192.168.123.117 metric 48
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + ip -6 route show
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: ::1 dev lo proto kernel metric 256 pref medium
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: fd2e:6f44:5dd8::8a dev br-ex proto kernel metric 48 pref medium
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: fd2e:6f44:5dd8::/64 dev br-ex proto ra metric 48 pref medium
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: fe80::/64 dev br-ex proto kernel metric 48 pref medium
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: fe80::/64 dev enp4s0 proto kernel metric 100 pref medium
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: default via fe80::5054:ff:fe74:c5e9 dev br-ex proto ra metric 48 pref medium
Jun 03 03:09:22 master-0-2 configure-ovs.sh[1971]: + exit 0
Comment 6 Jaime Caamaño Ruiz 2022-06-06 09:10:16 UTC 
*** Bug 2071574 has been marked as a duplicate of this bug. ***
Comment 8 errata-xmlrpc 2022-06-07 13:24:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.10.17 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4882
Note You need to log in before you can comment on or make changes to this bug.