Bug 1794053 - Control plane upgrade stuck while deleting SDN/OVS pods
Summary: Control plane upgrade stuck while deleting SDN/OVS pods
Keywords:
Status: CLOSED DUPLICATE of bug 1801445
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.11.z
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-22 15:09 UTC by Radomir Ludva
Modified: 2023-09-07 21:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-26 15:21:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.