-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13
-
None
-
No
-
SDN Sprint 233
-
1
-
Approved
-
False
-
Description of problem:
EgressFirewall status disappeared
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-03-02-234543
How reproducible:
Always
Steps to Reproduce:
1. Create a egressfirewall in a namespace 2. 3.
Actual results:
% oc get egressfirewall -n test1 NAME EGRESSFIREWALL STATUS default % oc get egressfirewall -n test1 -o yaml apiVersion: v1 items: - apiVersion: k8s.ovn.org/v1 kind: EgressFirewall metadata: creationTimestamp: "2023-03-03T08:35:05Z" generation: 2 name: default namespace: test1 resourceVersion: "187774" uid: 81e9cd11-9d40-493d-84f7-30a36e7c5de4 spec: egress: - to: nodeSelector: matchLabels: region: east user: qe type: Allow - to: cidrSelector: 0.0.0.0/0 type: Deny kind: List metadata: resourceVersion: "" 10823 E0303 08:50:08.963638 1 default_network_controller.go:705] Failed to update egress firewall status test1/default, error: error in updating status on EgressFirew all test1/default: EgressFirewall.k8s.ovn.org "default" is invalid: spec.egress[1].to: Too many: 2: must have at most 1 items 10824 I0303 08:50:08.963657 1 obj_retry.go:326] Retry add failed for *v1.EgressFirewall test1/default, will try again later: error in updating status on EgressFirewal l test1/default: EgressFirewall.k8s.ovn.org "default" is invalid: spec.egress[1].to: Too many: 2: must have at most 1 items
Expected results:
# oc get egressfirewall -n test1 NAME EGRESSFIREWALL STATUS default EgressFirewall Rules applied
Additional info:
- is cloned by
-
OCPBUGS-10744 [4.13] EgressFirewall status disappeared
- Closed
- is depended on by
-
OCPBUGS-10744 [4.13] EgressFirewall status disappeared
- Closed
- links to