Bug 2034097
| Summary: | [OVN] After edit EgressIP object, the status is not correct | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | huirwang |
| Component: | Networking | Assignee: | Ben Bennett <bbennett> |
| Networking sub component: | ovn-kubernetes | QA Contact: | Anurag saxena <anusaxen> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | anbhat, bpickard, dbrahane, jechen, surya |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-10 16:35:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
same behavior on GCP.
$ oc get node
NAME STATUS ROLES AGE VERSION
jechen-0108f-sbh2k-master-0.c.openshift-qe.internal Ready master 58m v1.22.1+6859754
jechen-0108f-sbh2k-master-1.c.openshift-qe.internal Ready master 59m v1.22.1+6859754
jechen-0108f-sbh2k-master-2.c.openshift-qe.internal Ready master 59m v1.22.1+6859754
jechen-0108f-sbh2k-worker-a-bbm2v.c.openshift-qe.internal Ready worker 48m v1.22.1+6859754
jechen-0108f-sbh2k-worker-b-nwtpx.c.openshift-qe.internal Ready worker 48m v1.22.1+6859754
$ oc label node jechen-0108f-sbh2k-worker-a-bbm2v.c.openshift-qe.internal "k8s.ovn.org/egress-assignable"=""
#initially egressIP is set to 10.0.128.111
$ cat config5.yaml
apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
name: egressip
spec:
egressIPs:
- 10.0.128.111
podSelector:
matchLabels:
team: blue
namespaceSelector:
matchLabels:
team: red
$ oc create -f ./SDN-1332-test/config5.yaml
egressip.k8s.ovn.org/egressip created
$ oc get egressip
NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS
egressip 10.0.128.111
$ oc get egressip
NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS
egressip 10.0.128.111 jechen-0108f-sbh2k-worker-a-bbm2v.c.openshift-qe.internal 10.0.128.111
$ oc get egressip -oyaml
apiVersion: v1
items:
- apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
creationTimestamp: "2022-01-09T00:30:16Z"
generation: 4
name: egressip
resourceVersion: "47832"
uid: b8dc4110-7f4a-45c1-abdb-17462466d51a
spec:
egressIPs:
- 10.0.128.111
namespaceSelector:
matchLabels:
team: red
podSelector:
matchLabels:
team: blue
status:
items:
- egressIP: 10.0.128.111
node: jechen-0108f-sbh2k-worker-a-bbm2v.c.openshift-qe.internal
kind: List
metadata:
resourceVersion: ""
selfLink: ""
# edit egressIP object to update egressIP to 10.0.128.222, now it shows both old egressIP address and new egressIP address are assigned to the node
$ oc get egressip
NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS
egressip 10.0.128.222 jechen-0108f-sbh2k-worker-a-bbm2v.c.openshift-qe.internal 10.0.128.111
$ oc get egressip -oyaml
apiVersion: v1
items:
- apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
creationTimestamp: "2022-01-09T00:30:16Z"
generation: 6
name: egressip
resourceVersion: "53039"
uid: b8dc4110-7f4a-45c1-abdb-17462466d51a
spec:
egressIPs:
- 10.0.128.222
namespaceSelector:
matchLabels:
team: red
podSelector:
matchLabels:
team: blue
status:
items:
- egressIP: 10.0.128.111
node: jechen-0108f-sbh2k-worker-a-bbm2v.c.openshift-qe.internal
- egressIP: 10.0.128.222
node: jechen-0108f-sbh2k-worker-a-bbm2v.c.openshift-qe.internal
kind: List
metadata:
resourceVersion: ""
selfLink: ""
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056 |
Description of problem: [OVN AWS] After edit EgressIP object, the status is not correct Version-Release number of selected component (if applicable): 4.10.0-0.ci-2021-12-19-184945 How reproducible: Always Steps to Reproduce: 1.Label two nodes as EgressIP nodes. 2.Create one EgressIP object with one EgressIP configured. oc get egressip -o yaml apiVersion: v1 items: - apiVersion: k8s.ovn.org/v1 kind: EgressIP metadata: creationTimestamp: "2021-12-20T05:52:31Z" generation: 3 name: egressip-1 resourceVersion: "106577" uid: 7c279c67-f9c1-40e8-9a6e-28e98a52cdd6 spec: egressIPs: - 10.0.77.135 namespaceSelector: matchLabels: name: test podSelector: {} status: items: - egressIP: 10.0.77.135 node: ip-10-0-77-132.us-east-2.compute.internal kind: List metadata: resourceVersion: "" selfLink: "" 3. Updated EgressIP 10.0.77.135 to another one 10.0.48.215 by "oc edit egressip egressip-1" 4. Check EgressIP object again. Actual results: The old EgressIP item was not removed from status, here it showed 2 EgressIPs items. $ oc get egressip -o yaml apiVersion: v1 items: - apiVersion: k8s.ovn.org/v1 kind: EgressIP metadata: creationTimestamp: "2021-12-20T05:52:31Z" generation: 5 name: egressip-1 resourceVersion: "107008" uid: 7c279c67-f9c1-40e8-9a6e-28e98a52cdd6 spec: egressIPs: - 10.0.48.215 namespaceSelector: matchLabels: name: test podSelector: {} status: items: - egressIP: 10.0.77.135 node: ip-10-0-77-132.us-east-2.compute.internal - egressIP: 10.0.48.215 node: ip-10-0-51-53.us-east-2.compute.internal kind: List metadata: resourceVersion: "" selfLink: "" Expected results: The old one should be removed from status. Additional info: