Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1794053

Summary:	Control plane upgrade stuck while deleting SDN/OVS pods
Product:	OpenShift Container Platform	Reporter:	Radomir Ludva <rludva>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Status:	CLOSED DUPLICATE	QA Contact:	Sunil Choudhary <schoudha>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	abraj, aos-bugs, aprajapa, armin.kunaschik, jokerman, mirollin, rphillips
Target Milestone:	---
Target Release:	3.11.z
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:	2020-03-26 15:21:50 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 Radomir Ludva 2020-01-22 15:09:08 UTC

Description of problem:
Upgrade from OCP v3.11.157 to OCP v3.11.161 stuck on:
TASK [openshift_node : Delete OpenShift SDN/OVS pods prior to upgrade]

It is important to manually delete the OVS pods in Terminating state from openshift-sdn namespace with:
$ oc delete pod ovs-_____ --grace-period=0 --force

Version-Release number of selected component (if applicable):
docker-1.13.1-108

Steps to Reproduce:
1. Create an OCP cluster for v3.11.157
2. Process yum update -y on all nodes to have the last release of docker-1.13.1-108
3. Process the upgrade control plane playbook:
   $ ansible-playbook -i hosts ./openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_11/upgrade_control_plane.yml


Actual results:
The upgrade process does not stuck.

Expected results:
OVS Pods are terminating regularly and the upgrade is finished without any issue.

Comment 2 Armin Kunaschik 2020-01-30 13:32:31 UTC

The description is actually wrong.

Actual results:
The upgrade process is stuck.

There is one week without any visible interaction or update. To me this does not reflect the high severity.

Comment 5 Ryan Phillips 2020-03-26 15:21:50 UTC


*** This bug has been marked as a duplicate of bug 1801445 ***