Bug 1610739
| Summary: | [WhnpxDH8] Incorrect initial state for Expand PVC | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> |
| Component: | Management Console | Assignee: | Ankush Behl <anbehl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.11.0 | CC: | aos-bugs, jokerman, mmccomas, spadgett, yapei |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 3.11.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: | 2018-08-13 18:34:29 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: | |||
1. Create StorageClass allow expansion 2. Create PVC using above storageclass created, set Capacity to 1GiB 3. When PVC is bound, open Expand PVC, no errors occurred, initial state shows 1GiB value Verified on registry.dev.redhat.io/openshift3/ose-web-console v3.11.0 2ec3cda22e18b 328MB |
Description of problem: Each time we open Expand PVC page, we will immediately got error message "The requested capacity may not be less than the current capacity" even we didn't change anything. Version-Release number of selected component (if applicable): OpenShift Web Console: v3.11.0-0.10.0 egistry.reg-aws.openshift.com:443/openshift3/ose-web-console v3.11 f2c8a01284df 4 days ago 318 MB How reproducible: Always Steps to Reproduce: 1.Setup env on EC2, create StorageClass, create PVC on web console and set request 2GiB $ cat > storageclass.yaml << EOF kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: expandsc provisioner: kubernetes.io/aws-ebs parameters: type: gp2 reclaimPolicy: Retain mountOptions: - debug allowVolumeExpansion: true EOF $ oc get pvc -o yaml apiVersion: v1 items: - apiVersion: v1 kind: PersistentVolumeClaim .... spec: accessModes: - ReadWriteOnce resources: requests: storage: 2Gi volumeName: pvc-2416ef08-9570-11e8-9849-0a649b5bdc56 status: accessModes: - ReadWriteOnce capacity: storage: 2Gi phase: Bound 2.PVC becomes Bound, Requested Capacity is set to 2GiB correctly, select Actions -> Expand PVC Actual results: 2.Error message "The requested capacity may not be less than the current capacity." always show up as initial state(the first time we open the Expand PVC dialog) Expected results: 3.Since we didn't set new PVC size yet, we should not do validation on unchanged value. Additional info: