Bug 2062666 - [4.10.z backport] configure-ovs: don't restart networking if not necessary
Summary: [4.10.z backport] configure-ovs: don't restart networking if not necessary
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Jaime Caamaño Ruiz
QA Contact: Ross Brattain
Depends On: 2062645
Blocks: 2070490
TreeView+ depends on / blocked
Reported: 2022-03-10 10:34 UTC by OpenShift BugZilla Robot
Modified: 2022-04-08 05:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2070490 (view as bug list)
Last Closed: 2022-04-08 05:04:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 3005 0 None open [release-4.10] Bug 2062666: configure-ovs: reload NM only when necessary 2022-03-10 10:35:08 UTC
Red Hat Product Errata RHSA-2022:1162 0 None Closed Unable to create loadbalancer.- While creating loadbalancer, provisioning_status and operating_status are marked as ERRO... 2022-05-17 00:32:13 UTC

Comment 2 Ross Brattain 2022-03-30 00:25:11 UTC

rebooted node to also check `rollback_nm`

configure-ovs.sh[1550] + for file in "${files[@]}"
configure-ovs.sh[1550] ++ basename ovs-port-phys0.nmconnection
configure-ovs.sh[1550] + file=ovs-port-phys0.nmconnection
configure-ovs.sh[1550] + file_path=/etc/NetworkManager/system-connections/ovs-port-phys0.nmconnection
configure-ovs.sh[1550] + '[' -f /etc/NetworkManager/system-connections/ovs-port-phys0.nmconnection ']'
configure-ovs.sh[1550] + rm -f /etc/NetworkManager/system-connections/ovs-port-phys0.nmconnection
configure-ovs.sh[1550] + echo 'Removed nmconnection file /etc/NetworkManager/system-connections/ovs-port-phys0.nmconnection'
configure-ovs.sh[1550] Removed nmconnection file /etc/NetworkManager/system-connections/ovs-port-phys0.nmconnection
configure-ovs.sh[1550] + nm_config_changed=1
configure-ovs.sh[1550] + ovs-vsctl --timeout=30 --if-exists del-br br-ex
configure-ovs.sh[1550] + '[' -d /sys/class/net/br-ex1 ']'
configure-ovs.sh[1550] + echo 'OVS configuration successfully reverted'
configure-ovs.sh[1550] OVS configuration successfully reverted
configure-ovs.sh[1550] + reload_nm
configure-ovs.sh[1550] + '[' 1 -eq 0 ']'
configure-ovs.sh[1550] + nm_config_changed=0
configure-ovs.sh[1550] + echo 'Reloading NetworkManager after configuration changes...'
configure-ovs.sh[1550] Reloading NetworkManager after configuration changes...
configure-ovs.sh[1550] + nmcli network off
configure-ovs.sh[1550] + systemctl restart NetworkManager
configure-ovs.sh[1550] + nmcli network on
configure-ovs.sh[1550] + nm-online -s -t 60
configure-ovs.sh[1550] [234B blob data]
configure-ovs.sh[1550] + echo 'NetworkManager has activated all suitable profiles after reload'
configure-ovs.sh[1550] NetworkManager has activated all suitable profiles after reload
configure-ovs.sh[1550] + nm-online -t 0
configure-ovs.sh[1550] + echo 'NetworkManager has connectivity after reload'
configure-ovs.sh[1550] NetworkManager has connectivity after reload
configure-ovs.sh[1550] + print_state

Comment 7 errata-xmlrpc 2022-04-08 05:04:20 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 (Important: OpenShift Container Platform 4.10.8 bug fix and security 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.


Note You need to log in before you can comment on or make changes to this bug.