Bug 2089807

Summary: Many errors when powering off a master
Product: OpenShift Container Platform Reporter: Shubham pawar <shpawar>
Component: NetworkingAssignee: Mohamed Mahmoud <mmahmoud>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: dwest, ffernand, lmicozzi, openshift-bugs-escalate, srengan, surya, zzhao
Version: 4.8   
Target Milestone: ---   
Target Release: 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-17 19:48:59 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:

Description Shubham pawar 2022-05-24 13:32:30 UTC
Description of problem:

During the validation test of the cluster install we shut off one of the masters, we are expecting no issues but `oc commands` and the console are getting errors:
[root@amssv0545 ~]# oc run -it --rm ha-test --image=curlimages/curl --restart=Never -- sh
pod "ha-test" deleted
error: timed out waiting for the condition

4.8 cluster, after power off of a master node ( among 3 ), there were issues with the OVN-Kubernetes on the remaining nodes, and the problem has been solved by applying the delete(and consequently restart) of OVN Kubernetes pods on the master nodes, as specified in the solution https://access.redhat.com/solutions/6646561.

Comment 12 zhaozhanqi 2022-08-16 08:09:43 UTC
This issue cannot be reproduced even power off or restart the leader master on 4.12.0-0.nightly-2022-08-15-150248
Move this bug to verified.

Comment 15 errata-xmlrpc 2023-01-17 19:48:59 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 (Moderate: OpenShift Container Platform 4.12.0 bug fix and 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:7399