Bug 1744893
| Summary: | PVC should update the event after resizing finish successfully | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Chao Yang <chaoyang> |
| Component: | Storage | Assignee: | Hemant Kumar <hekumar> |
| Status: | CLOSED ERRATA | QA Contact: | Chao Yang <chaoyang> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.2.0 | CC: | aos-bugs, aos-storage-staff, ckoep, fbertina, hekumar, piqin |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| 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: | 2019-10-16 06:37:16 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: | |||
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 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 |
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: