-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.10.z
-
None
Description of problem:
For some reason, the LSP of a pod is not properly added to the port group where the ACL of a NetworkPolicy is applied. This results on the networkpolicy not being applied to the pod and communication not possible.
Version-Release number of selected component (if applicable):
4.10
How reproducible:
Always with a concrete pod at customer environment.
Steps to Reproduce:
(not known exactly yet)
Actual results:
LSP not in port group. ACL not applied. Netpol not in effect.
Expected results:
LSP in port group. ACL applied. Netpol in effect.
Additional info:
Details in private comments, as they involve sensitive data. Deleting the pod does nothing, but it is possible that this has something to do with the pod being recreated with the same name (although the LSPs UUIDs are different in each incarnation).
- clones
-
OCPBUGS-4837 [4.12] Pod LSP missing from PortGroup
- Closed
- depends on
-
OCPBUGS-4837 [4.12] Pod LSP missing from PortGroup
- Closed
- is cloned by
-
OCPBUGS-4839 [4.10] Pod LSP missing from PortGroup
- Closed
- is depended on by
-
OCPBUGS-4839 [4.10] Pod LSP missing from PortGroup
- Closed
- links to