-
Bug
-
Resolution: Done
-
Major
-
None
-
4.12.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
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:
- depends on
-
OCPBUGS-4626 [4.13] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)
-
- Release Pending
-
- is cloned by
-
OCPBUGS-4626 [4.13] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)
-
- Release Pending
-
-
OCPBUGS-4390 [4.11.z] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)
-
- Closed
-
-
OCPBUGS-4391 [4.10.z] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)
-
- Closed
-
-
OCPBUGS-4392 [4.9.z] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)
-
- Closed
-
-
OCPBUGS-4394 [4.8.z] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)
-
- Closed
-
- is depended on by
-
OCPBUGS-4390 [4.11.z] Sriov-network-operator does not detect changes to Machine Config (when updating the machine config)
-
- Closed
-
- links to