Bug 1889420 - OCP failed to add vsphere disk when pod moved to new node during cluster upgrade
Summary: OCP failed to add vsphere disk when pod moved to new node during cluster upgrade
Keywords:
Status: POST
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Hemant Kumar
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-19 15:55 UTC by Neil Girard
Modified: 2020-11-17 00:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Github openshift kubernetes pull 445 None open Bug 1889420: Add dangling volume check for vsphere 2020-11-10 15:06:51 UTC

Description Neil Girard 2020-10-19 15:55:06 UTC
Description of problem:

Volumes for Jenkins pods failed to mount during upgrade of cluster.  Had to manually go into vSphere to remove them from old node so new node could pick them up.

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

OCP 4.4

How reproducible:

Rare.

Actual results:

Many volumes failed to attach to pods

Expected results:

No volume failures when moving pods

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

kubernetes.io/vsphere-volume

Additional info:


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