-
Bug
-
Resolution: Done
-
Major
-
4.12
-
None
-
No
-
Rejected
-
False
-
Description of problem:
The verifications that kubernetes-nmstate runs after applying a policy do not work in single stack IPv6. They only check for IPv4 connectivity which will never be present in a single stack v6 cluster.
Version-Release number of selected component (if applicable):
Everything before 4.14
How reproducible:
Always
Steps to Reproduce:
1. Deploy operator into single stack v6 cluster 2. Apply any NNCP 3.
Actual results:
NNCP fails to apply due to verification error
Expected results:
NNCP applies successfully
Additional info:
This was already fixed in 4.14 as part of https://issues.redhat.com/browse/OPNET-227 . It was tracked as an epic because of the significant test work needed. However, I do consider it a bug because we did not ship previous releases with the understanding (or any documentation) that this did not work. It was simply a hole in our testing.
Also, the fix is relatively simple so backporting is not high risk in this case.
- blocks
-
OCPBUGS-18463 Kubernetes-NMState does not work in single stack IPv6 clusters
- Closed
- is cloned by
-
OCPBUGS-18463 Kubernetes-NMState does not work in single stack IPv6 clusters
- Closed
- is related to
-
OPNET-348 Backport IPv6 fix in kubernetes-nmstate to 4.12
- Dev Complete