Bug 2113860 - After node re-created, some ovn annotations are not found for the node and due to that pod is in crashloop
Summary: After node re-created, some ovn annotations are not found for the node and du...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.z
Assignee: Miguel Duarte Barroso
QA Contact: Anurag saxena
Depends On: 2068910
Blocks: 2113861
TreeView+ depends on / blocked
Reported: 2022-08-02 07:51 UTC by Miguel Duarte Barroso
Modified: 2022-08-29 06:47 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2068910
Last Closed: 2022-08-29 06:46:55 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 1226 0 None open [release-4.11] Bug 2113860: reconcile-node-lbs 2022-08-11 08:03:28 UTC
Red Hat Product Errata RHBA-2022:6143 0 None None None 2022-08-29 06:47:13 UTC

Comment 2 zhaozhanqi 2022-08-19 01:09:55 UTC
@Polina Rabinovich Could you again help verified this bug on 4.11 version since you did 4.12 version? thanks.

Comment 3 Polina Rabinovich 2022-08-23 05:01:37 UTC
yes, sure

Comment 4 Polina Rabinovich 2022-08-23 10:01:19 UTC
Verified in 4.11.0-0.nightly-2022-08-22-195828:
[kni@provisionhost-0-0 ~]$ oc version

Client Version: 4.11.0-0.nightly-2022-08-22-195828
Kustomize Version: v4.5.4
Server Version: 4.11.0-0.nightly-2022-08-22-195828
Kubernetes Version: v1.24.0+b62823b

I ran remediation process 6 times (using Node Deletion strategy) and all pods are Running:

[kni@provisionhost-0-0 ~]$ oc get pods -o wide -n openshift-operators
NAME                                                            READY   STATUS    RESTARTS      AGE     IP             NODE         NOMINATED NODE   READINESS GATES
node-healthcheck-operator-controller-manager-66c7648d44-xf88m   2/2     Running   0             53m   master-0-0   <none>           <none>
self-node-remediation-controller-manager-667dfb7f7f-ws626       1/1     Running   1 (52m ago)   53m    worker-0-2   <none>           <none>
self-node-remediation-ds-9b4qv                                  1/1     Running   0             52m    worker-0-2   <none>           <none>
self-node-remediation-ds-ktdtf                                  1/1     Running   0             52m    worker-0-1   <none>           <none>
self-node-remediation-ds-lfflf                                  1/1     Running   0             2m54s     worker-0-0   <none>           <none>

[kni@provisionhost-0-0 ~]$ oc get nodes
master-0-0   Ready    master   4h      v1.24.0+b62823b
master-0-1   Ready    master   4h      v1.24.0+b62823b
master-0-2   Ready    master   4h      v1.24.0+b62823b
worker-0-0   Ready    worker   2m51s   v1.24.0+b62823b
worker-0-1   Ready    worker   3h38m   v1.24.0+b62823b
worker-0-2   Ready    worker   3h37m   v1.24.0+b62823b

Comment 7 errata-xmlrpc 2022-08-29 06:46:55 UTC
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 (OpenShift Container Platform 4.11.2 bug fix 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.


Note You need to log in before you can comment on or make changes to this bug.