Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2105884

Summary:	SR-IOV and nmstate NIC configuration order issue
Product:	OpenShift Container Platform	Reporter:	Takayoshi Kimura <tkimura>
Component:	Networking	Assignee:	Ben Nemec <bnemec>
Networking sub component:	kubernetes-nmstate-operator	QA Contact:	Aleksandra Malykhin <amalykhi>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium
Version:	4.10
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-28 21:49:47 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:

Description Takayoshi Kimura 2022-07-11 05:01:53 UTC

Description of problem:

Using SR-IOV and nmstate operators, try to apply the following configurations to the hosts with SR-IOV NIC:

- nmstate to configure the NIC with MTU 9000 and create MTU 9000 VLANIF
- SR-IOV to create MTU 9000 VFs

When provisioning a new node with labels to apply both SR-IOV and nmstate, it seems that the SR-IOV and nmstate configurations are done in a random order and it will get different outcomes.

First nmstate when SR-IOV, the configuration is done as expected.

First SR-IOV then nmstate, SR-IOV VFs will be deleted when the nmstate configuration ran.

Version-Release number of selected component (if applicable):

- 4.10.13
- kubernetes-nmstate-operator.4.10.0-202205120735
- sriov-network-operator.4.10.0-202205251117

How reproducible:

Always

Steps to Reproduce:
1. Configure SR-IOV NIC with both SR-IOV and nmstate operators
2.
3.

Actual results:

See description.

Expected results:

Declared configuration applied correctly, regardless of the SR-IOV and nmstate operator execution order. 

Additional info:

Comment 2 Takayoshi Kimura 2022-07-11 05:29:05 UTC

Another configuraion attempt.

When creating VFs with MTU 9000 using SR-IOV operator, it also configures the NIC with MTU 9000. So user tried the following configuration:

- nmstate to create MTU 9000 VLANIF
- SR-IOV to configure VFs with MTU 9000 (also set physical NIC with MTU 9000)

In this case, first SR-IOV then nmstate, the configuration is done as expected.

First nmstate then SR-IOV, nmstate fails to create VLANIFs (because MTU 9000 is not set yet) and no retry even after SR-IOV configuration is done.

Comment 3 Ben Nemec 2022-07-28 21:49:47 UTC

This appears to be reporting essentially the same thing as 2105141.

*** This bug has been marked as a duplicate of bug 2105141 ***