Red Hat Bugzilla – Bug 1532986
PVC condition is still Resizing after Resizing is finished
Last modified: 2018-03-28 10:19:33 EDT
Description of problem: PVC condition is still Resizing after Resizing is finished Version-Release number of selected component (if applicable): oc v3.9.0-0.15.0 kubernetes v1.9.0-beta1 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-172-18-14-74.ec2.internal:8443 openshift v3.9.0-0.15.0 kubernetes v1.9.0-beta1 How reproducible: Always Steps to Reproduce: 1.Create a dynamic pvc oc create -f https://raw.githubusercontent.com/chao007/v3-testfiles/master/persistent-volumes/ebs/dynamic-provisioning/pvc.yaml 2.Create a pod oc create -f https://raw.githubusercontent.com/chao007/v3-testfiles/master/persistent-volumes/ebs/pod.yaml 3.After pod is running, edit pvc, requested storage from 4Gi to 6Gi 4.Wait for pv storage resize to 6Gi 5.Delete pod and recreat it 6.Check pod is running and storage resized to 6Gi 7.Check pvc yaml file -bash-4.2# oc get pvc -o yaml apiVersion: v1 items: - apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" pv.kubernetes.io/bound-by-controller: "yes" volume.beta.kubernetes.io/storage-class: foo volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/aws-ebs creationTimestamp: 2018-01-10T06:42:29Z name: ebsc namespace: chao resourceVersion: "29961" selfLink: /api/v1/namespaces/chao/persistentvolumeclaims/ebsc uid: 6d95478d-f5d1-11e7-92cd-0edfbad2900e spec: accessModes: - ReadWriteOnce resources: requests: storage: 6Gi volumeName: pvc-6d95478d-f5d1-11e7-92cd-0edfbad2900e status: accessModes: - ReadWriteOnce capacity: storage: 6Gi conditions: - lastProbeTime: null lastTransitionTime: 2018-01-10T06:53:25Z status: "True" type: Resizing phase: Bound kind: List metadata: resourceVersion: "" selfLink: "" Actual results: PVC status.conditions.type is still Resizing Expected results: PVC status should update Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
There is a commit missing from openshift origin alpha releases which was include in standard 1.9.0 k8s release - https://github.com/kubernetes/kubernetes/pull/56587 The above commit makes sure that Conditions is reset once resizing has been finished. This commit is missing from origin unfortunately. I spoke with deads and this happened because origin was rebased with 1.9.0-beta and not final product. There is a rebase PR open - https://github.com/openshift/origin/pull/18003/files which will bring all the latest stuff from upstream 1.9 branch and that will include fix for this bug too.
This should be available in latest builds now.
Verified on oc v3.9.0-0.31.0 kubernetes v1.9.1+a0ce1bc657 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-172-18-1-24.ec2.internal:443 openshift v3.9.0-0.31.0 kubernetes v1.9.1+a0ce1bc657 After resizing, pvc yaml file is like below: [root@ip-172-18-1-24 ~]# oc get pvc ebsc -o yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" pv.kubernetes.io/bound-by-controller: "yes" volume.beta.kubernetes.io/storage-class: foo volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/aws-ebs creationTimestamp: 2018-01-29T03:10:10Z name: ebsc namespace: default resourceVersion: "9790" selfLink: /api/v1/namespaces/default/persistentvolumeclaims/ebsc uid: ea532ba6-04a1-11e8-bd3d-0ec8176f823a spec: accessModes: - ReadWriteOnce resources: requests: storage: 6Gi volumeName: pvc-ea532ba6-04a1-11e8-bd3d-0ec8176f823a status: accessModes: - ReadWriteOnce capacity: storage: 6Gi phase: Bound
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-2018:0489