Bug 1744893 - PVC should update the event after resizing finish successfully
Summary: PVC should update the event after resizing finish successfully
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.2.0
Assignee: Hemant Kumar
QA Contact: Chao Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-23 06:50 UTC by Chao Yang
Modified: 2023-09-07 20:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:37:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 23683 0 None closed Bug 1744893: Fix error event when cinder volume is expanded online 2021-01-26 17:50:04 UTC
Red Hat Knowledge Base (Solution) 4445851 0 None None None 2019-10-22 12:38:56 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:37:27 UTC

Description Chao Yang 2019-08-23 06:50:54 UTC 
Description of problem:
PVC should update the event after resizing finish successfully

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-08-22-153337

How reproducible:
Always

Steps to Reproduce:
1.Create pvc, pod.
2.Resizing pvc spec.resources.requests.storage from 1Gi to 2Gi
3.Delete pod
4.After pv is resized from 1Gi to 2Gi, Create pod again
5.Check pvc status
oc describe pvc pvc4
Name:          pvc4
Namespace:     storage
StorageClass:  standard
Status:        Bound
Volume:        pvc-9495ca78-c56e-11e9-9e50-fa163e923999
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/cinder
               volume.kubernetes.io/selected-node: preserve-groupg-4cf4r-worker-thlsr
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      2Gi
Access Modes:  RWO
VolumeMode:    Filesystem
Events:
  Type       Reason                 Age                From                         Message
  ----       ------                 ----               ----                         -------
  Normal     WaitForFirstConsumer   17m (x4 over 17m)  persistentvolume-controller  waiting for first consumer to be created before binding
  Normal     ProvisioningSucceeded  17m                persistentvolume-controller  Successfully provisioned volume pvc-9495ca78-c56e-11e9-9e50-fa163e923999 using kubernetes.io/cinder
  Warning    VolumeResizeFailed     16m                volume_expand                error expanding volume "storage/pvc4" of plugin "kubernetes.io/cinder": volume status is not available
Mounted By:  pod4

Actual results:
No Resizing successfully event 

Expected results:
Should add Resizing successfully event

Additional info:
Comment 4 Chao Yang 2019-09-04 03:00:44 UTC 
It is passed on 4.2.0-0.nightly-2019-09-02-172410

  Warning    VolumeResizeFailed     45s (x2 over 7m22s)  volume_expand                error expanding volume "default/pvc5" of plugin "kubernetes.io/cinder": volume in in-use status can not be expanded, it must be available and not attached to a node
Comment 8 errata-xmlrpc 2019-10-16 06:37:16 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, 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/RHBA-2019:2922
Note You need to log in before you can comment on or make changes to this bug.