Loading...

XML

Word

Printable

Type: Bug
Resolution: Cannot Reproduce
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.13.z, 4.14.z
Component/s: Storage / Kubernetes External Components
Labels:
- csi

Activity Type:
Quality / Stability / Reliability
Blocked:
True
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Important
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Review Complete:
PX Priority Data:
PX Impact Score:
PX Technical Impact:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

VMware OCP Upgrade stuck 4.13.42 -> 4.14.26, stuck with image-registry pod failing in "containercreating" due to FailedMount.

Warning FailedMount 3m25s (x11 over 141m) kubelet Unable to attach or mount volumes: unmounted volumes=[registry-storage], unattached volumes=[trusted-ca installation-pull-secrets bound-sa-token kube-api-access-9cbkm registry-storage registry-tls ca-trust-extracted registry-certificates]: timed out waiting for the condition Warning FailedAttachVolume 9s (x82 over 151m) attachdetach-controller AttachVolume.Attach failed for volume "pvc-b11a0b26-7c85-479c-a738-1543a80793cb" 
  * As a workaround, we  created a new PVC using  `thin-csi`StorageClass to allow the upgrade to proceed.

Other clusters with the same configuration did not see the issue while upgrading, while using the default `thin` StorageClass.

Assignee:: Hemant Kumar

Reporter:: Abdoul Djire

Need Info From:: Abdoul Djire

Contributors:: None

QA Contact:: Wei Duan

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2025/03/31 3:34 PM

Updated:: 2025/09/13 5:24 PM

Resolved:: 2025/05/07 5:16 PM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates