Bug 1719686

Summary:	Not able to resize ceph volume
Product:	OpenShift Container Platform	Reporter:	Rajnikant <rkant>
Component:	Storage	Assignee:	Hemant Kumar <hekumar>
Status:	CLOSED ERRATA	QA Contact:	Liang Xia <lxia>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.11.0	CC:	aos-bugs, aos-storage-staff, bchilds, hekumar, lxia, rhowe
Target Milestone:	---	Keywords:	Reopened
Target Release:	3.11.z
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-12-16 11:57:10 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:
Bug Depends On:	1779531
Bug Blocks:

Description Rajnikant 2019-06-12 10:51:06 UTC

Description of problem:
Not able to resize ceph volume. 

Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.11

How reproducible:

oc version
oc v3.11.98

Throwing error

 VolumeResizeFailed Error expanding volume "test-project/test-ceph" of plugin kubernetes.io/rbd : rbd info failed, error: can not get image size info 

Steps to Reproduce:
1.
2.
3.

Actual results:
failed.

Expected results:
Should resize

Additional info:
Will provide additional information.

Comment 14 Liang Xia 2019-12-10 02:46:06 UTC

openshift v3.11.157
kubernetes v1.11.0+d4cacc0


# oc get pvc
NAME      STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS         AGE
mysql     Bound     pvc-a7c1d05d-1a4c-11ea-814d-fa163eb6601c   1Gi        RWO            cephrbdprovisioner   20h


# oc edit pvc mysql
persistentvolumeclaim/mysql edited


# oc describe pvc
Name:          mysql
Namespace:     lxiap
StorageClass:  cephrbdprovisioner
Status:        Bound
Volume:        pvc-a7c1d05d-1a4c-11ea-814d-fa163eb6601c
Labels:        app=mysql-persistent
               template=mysql-persistent-template
Annotations:   openshift.io/generated-by=OpenShiftNewApp
               pv.kubernetes.io/bind-completed=yes
               pv.kubernetes.io/bound-by-controller=yes
               volume.beta.kubernetes.io/storage-provisioner=kubernetes.io/rbd
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      1Gi
Access Modes:  RWO
Conditions:
  Type                      Status  LastProbeTime                     LastTransitionTime                Reason  Message
  ----                      ------  -----------------                 ------------------                ------  -------
  FileSystemResizePending   True    Mon, 01 Jan 0001 00:00:00 +0000   Mon, 09 Dec 2019 21:36:14 -0500           Waiting for user to (re-)start a pod to finish file system resize of volume on node.
Events:                     <none>


# oc scale --replicas=0 dc/mysql
# sleep 60
# oc scale --replicas=1 dc/mysql


# oc get pvc
NAME      STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS         AGE
mysql     Bound     pvc-a7c1d05d-1a4c-11ea-814d-fa163eb6601c   2Gi        RWO            cephrbdprovisioner   20h


# oc describe pvc mysql
Name:          mysql
Namespace:     lxiap
StorageClass:  cephrbdprovisioner
Status:        Bound
Volume:        pvc-a7c1d05d-1a4c-11ea-814d-fa163eb6601c
Labels:        app=mysql-persistent
               template=mysql-persistent-template
Annotations:   openshift.io/generated-by=OpenShiftNewApp
               pv.kubernetes.io/bind-completed=yes
               pv.kubernetes.io/bound-by-controller=yes
               volume.beta.kubernetes.io/storage-provisioner=kubernetes.io/rbd
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      2Gi
Access Modes:  RWO
Events:        <none>


# oc rsh pod/mysql-2-c4n2h
sh-4.2$ df -h /var/lib/mysql/data
Filesystem      Size  Used Avail Use% Mounted on
/dev/rbd0       2.0G  191M  1.8G  10% /var/lib/mysql/data

Comment 16 errata-xmlrpc 2019-12-16 11:57:10 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:4050