-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.12
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
For some reason the NMState package being used right now is nmstate-1.3.3-1.el8.x86_64. We're looking for a fix that was verified in 1.3.3-6, but even though that should be available by now it isn't showing up in our images. Another odd thing is that 1.3.3 appears to be the RHEL 8.7 NMState version, whereas we are based on 8.6 elsewhere in 4.12. I'm opening this to track our investigation of how this came about and what we can do to get NMState to a more current version.
Version-Release number of selected component (if applicable):
4.12
How reproducible:
Always
Steps to Reproduce:
1. Deploy Kubernetes-NMState 2. Inside one of the handler pods, run "nmstatectl --version". 3.
Actual results:
Version is 1.3.3-1
Expected results:
Version is 1.3.3-6 or newer
Additional info:
This is a followup to https://issues.redhat.com/browse/OCPBUGS-3394 . I'm opening a separate bug to avoid confusion about what we're trying to fix right now.
- is depended on by
-
OCPBUGS-3394 Dual stack SNO fails because of networking
-
- Closed
-