Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Major
Fix Version/s: None
Affects Version/s: 4.8.z
Component/s: Networking / SR-IOV
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:

4.8.z
Release Blocker:
Rejected
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

Sriov-network-operator controller does not detect changes to the machine config when the files within the Sriov-network-operator controller pod are different then the rendered machine config in OCP.

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

How reproducible:

Always

Steps to Reproduce:

1. Change a file in /bindata/manifests
2. Compile the sriov-network-operator controller
3. Load the new controller.
4. You will get "syncOvsHardwareOffloadMachineConfigs    No content change, skip updating MC" in the logs when the machine config should have changed.

Actual results:

Machine Config is not updated on the nodes.

Expected results:

Machine Config is updated on the nodes.

Additional info:

clones

OCPBUGS-4140 [4.12] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)

Closed

depends on

OCPBUGS-4392 [4.9.z] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)

Closed

Assignee:: William Zhao

Reporter:: William Zhao

Need Info From:: None

Contributors:: None

QA Contact:: Zhanqi Zhao

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2022/12/01 7:20 PM

Updated:: 2025/07/28 5:36 PM

Resolved:: 2022/12/07 10:48 PM