Bug 1971262

Summary: Update nmstate version in CNV
Product: Container Native Virtualization (CNV) Reporter: Ofir Nash <onash>
Component: NetworkingAssignee: Petr Horáček <phoracek>
Status: CLOSED ERRATA QA Contact: Ofir Nash <onash>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.8.0CC: cnv-qe-bugs
Target Milestone: ---   
Target Release: 4.8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kubernetes-nmstate-handler-container-v4.8.1-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-24 12:48:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
bond-fail-over-mac.yaml
none
bridge-on-bond none

Description Ofir Nash 2021-06-13 08:50:32 UTC 
Description of problem:
nmstate version out of date in CNV. There are some bug fixes that have been fixed in nmstate-1.0.2-11 and in our environments we have 1.0.2-5.

This came up from our issue when trying to create a bridge on a bond defined with fail_over_mac option activated, we fail with an error (we don't specify any MAC address).
This issue has been fixed from version nmstate-1.0.2-11.


Version-Release number of selected component (if applicable):
nmstate-1.0.2-5.el8


How reproducible:
Always


Steps to Reproduce:
1. Create bond defined with fail_over_mac activated (attached yaml - adjust accordingly to worker and slaves)
> oc apply -f bond-fail-over-mac.yaml
2. Create bridge on the bond defined (attached yaml - adjust accordingly to worker)
> oc apply -f bridge-on-bond.yaml


Actual results:
libnmstate.error.NmstateValueError: MAC address cannot be specified in bond interface along with fail_over_mac active on active backup mode
'
    Reason:                FailedToConfigure
(oc describe nnce <NNCE_NAME>)


Expected results:
Configures Successfuly 
(oc get nncp <nncp_name>)


Additional info:
* How to check for nmstate version in the cluster: 
1. `oc exec -it -n openshift-cnv <nmstate-handler-pod-name> bash`
2. Once in bash: `rpm -qi nmstate`

Output:
Name        : nmstate
Version     : 1.0.2
Release     : 5.el8

* Same scenario as in bug: https://bugzilla.redhat.com/show_bug.cgi?id=1896619 which now has been fixed.
Comment 1 Ofir Nash 2021-06-13 10:56:52 UTC 
Created attachment 1790690 [details]
bond-fail-over-mac.yaml
Comment 2 Ofir Nash 2021-06-13 10:58:30 UTC 
Created attachment 1790691 [details]
bridge-on-bond
Comment 3 Ofir Nash 2021-08-17 13:29:30 UTC 
Verified the scenario with the nmstate and nmstate-handler version needed:

Name        : nmstate
Version     : 1.0.2
Release     : 11.el8_4

nmstate-handler version is: v4.8.1-2


Scenario checked:
1. Created bond with fail_over_mac option activated (From attached yaml - adjusted node and slaves. Added MTU 1400)
2. Created bridge on bond (From attached yaml - adjusted node)
3. Verified both have been SuccessfullyConfigured.
Comment 8 errata-xmlrpc 2021-08-24 12:48:59 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 (Moderate: OpenShift Virtualization 4.8.1 Images security and 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/RHSA-2021:3259