Bug 2022646
| Summary: | configure-ovs.sh failure - Error: unknown connection 'WARN:' | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yurii Prokulevych <yprokule> |
| Component: | Machine Config Operator | Assignee: | Yurii Prokulevych <yprokule> |
| Machine Config Operator sub component: | platform-baremetal | QA Contact: | Yurii Prokulevych <yprokule> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | aos-bugs, tsedovic, vvoronko |
| Version: | 4.8 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: warning message sent by 'clone_slave_connection' function was stored in a 'new_uuid' variable which is intended to store just connection's UUID
Consequence: nmcli commands that reference 'new_uuid' variable as input were failing due to incorrect value being stored in the 'new_uuid' variable
Fix: warning message from 'clone_slave_connection' function is redirected to stderr
Result: nmcli commands that reference 'new_uuid' variable don't fail due to unknown connection
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-10 16:26:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2022641 | ||
|
Description
Yurii Prokulevych
2021-11-12 09:24:37 UTC
Yurii - it looks like you created the fix for this so reassigning this to you. Verified with 4.10.0-0.nightly-2021-11-15-034648
Fix present in configure-ovs.sh:
```
if nmcli connection show id "${new_name}" &> /dev/null; then
echo "WARN: existing ovs slave ${new_name} connection profile file found, overwriting..." >&2
nmcli connection delete id "${new_name}" &> /dev/null
fi
```
Rebooting nodes multiple times and issue didn't reproduce
systemctl status ovs-configuration.service
● ovs-configuration.service - Configures OVS with proper host networking configuration
Loaded: loaded (/etc/systemd/system/ovs-configuration.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Thu 2021-11-18 12:24:20 UTC; 1min 0s ago
Main PID: 4125 (code=exited, status=0/SUCCESS)
CPU: 190ms
Nov 18 12:24:20 worker-0-0 configure-ovs.sh[4125]: + '[' -f /etc/ovnk/extra_bridge ']'
Nov 18 12:24:20 worker-0-0 configure-ovs.sh[4125]: + nmcli connection show br-ex1
Nov 18 12:24:20 worker-0-0 configure-ovs.sh[4125]: + nmcli connection show ovs-if-phys1
Nov 18 12:24:20 worker-0-0 configure-ovs.sh[4125]: + '[' '!' -f /etc/ovnk/extra_bridge ']'
Nov 18 12:24:20 worker-0-0 configure-ovs.sh[4125]: + ovs-vsctl --timeout=30 --if-exists del-br br0
Nov 18 12:24:20 worker-0-0 ovs-vsctl[4147]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=30 --if-exists del-br br0
Nov 18 12:24:20 worker-0-0 configure-ovs.sh[4125]: + exit 0
Nov 18 12:24:20 worker-0-0 systemd[1]: ovs-configuration.service: Succeeded.
Nov 18 12:24:20 worker-0-0 systemd[1]: Started Configures OVS with proper host networking configuration.
Nov 18 12:24:20 worker-0-0 systemd[1]: ovs-configuration.service: Consumed 190ms CPU time
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 (Moderate: OpenShift Container Platform 4.10.3 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. https://access.redhat.com/errata/RHSA-2022:0056 |