origin
origin copied to clipboard
openshift
Cannot resize Ceph RBD PVC
Hello,
I have an issue with extending pvc based on ceph RBD image. I've created storageclass with allowVolumeExpansion: true parameter to allow pvc expansion for users. However it seems to not working properly with my current setup of OKD. When I set new size for PVC i get following error:
Error expanding volume "xxxx" of plugin kubernetes.io/rbd : rbd info failed, error: can not get image size info kubernetes-dynamic-pvc-3629a9c1-7090-11e9-9aaf-005056ab27db rbd image 'kubernetes-dynamic-pvc-3629a9c1-7090-11e9-9aaf-005056ab27db': size 1GiB in 256 objects order 22 (4MiB objects) block_name_prefix: rbd_data.a3cc26b8b4567 format: 2 features: flags: create_timestamp: Tue May 7 06:20:32 2019
My ceph cluster version is luminous 12.2.12
Version
oc v3.11.0+62803d0-1 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO
openshift v3.11.0+d0c29df-98 kubernetes v1.11.0+d4cacc0
Steps To Reproduce
- Create pvc
- Extend pvc
- Wait for pvc to complete resize
Current Result
PVC hangs at "Resizing" and no resize operation is going to happen.
Expected Result
PVC should resize and wait for container to recreate with info:
message: Waiting for user to (re-)start a pod to finish file system resize of volume on node. type: FileSystemResizePending
Additional Information
Upgrading to newest version of 3.11 OKD did not solve the problem. When trying same operation in my dev environment whole operation succeded and my pvc is expanded. This is older version of OKD:
oc v3.11.0+62803d0-1 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO
openshift v3.11.0+1c3e643-87 kubernetes v1.11.0+d4cacc0
Can this issue be related to version od OKD? I need this functionality to work with my current version of OKD, but also with newer version in future.
When asked about it, the redhat support answered : "maybe in 4.x"
Le jeu. 8 août 2019 à 09:56, anvpetrov [email protected] a écrit :
Same problem with 3.11.129 and CEPH RBD resize
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/openshift/origin/issues/22789?email_source=notifications&email_token=AALO7WTCAUJLVHXKJOO4A7DQDPGSFA5CNFSM4HLF6M4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD32ZLFI#issuecomment-519411093, or mute the thread https://github.com/notifications/unsubscribe-auth/AALO7WUHQBHJSM2JKLEJCWDQDPGSFANCNFSM4HLF6M4A .
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
