Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot resize Ceph RBD PVC #22789

Open
hniedlich opened this issue May 7, 2019 · 7 comments
Open

Cannot resize Ceph RBD PVC #22789

hniedlich opened this issue May 7, 2019 · 7 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@hniedlich
Copy link

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
  1. Create pvc
  2. Extend pvc
  3. 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.

@Blaiserman
Copy link

any update on this?

@sn1ce
Copy link

sn1ce commented Jun 19, 2019

Same issue for me.
It doesnt changed the size of the pvc...

@anvpetrov
Copy link

Same problem with 3.11.129 and CEPH RBD resize

@h4wkmoon
Copy link

h4wkmoon commented Aug 8, 2019 via email

@openshift-bot
Copy link
Contributor

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

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 6, 2019
@openshift-bot
Copy link
Contributor

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

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 6, 2019
@devopstales
Copy link

/remove-lifecycle stale
/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Dec 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

8 participants