Hello, I did found out how to resolve this issue. In Rocky the default versions for kubernets and cloud manager are pretty old. I fixed it by creating a template with the following labels: --labels kube_tag=v1.13.4,cloud_provider_tag=1.13.1,kube_version=v1.13.4 On Thu, Apr 11, 2019 at 2:14 PM Ionut Biru <ionut@fleio.com> wrote:

Hello,

I'm trying to deploy a simple wordpress installation following the documentation from kubernets.

https://kubernetes.io/docs/tutorials/stateful-application/mysql-wordpress-pe...

kubernets was deployed using magnum on openstack rocky using the following template: https://paste.xinu.at/sRk/

Then i'm using the cinder storage class that is described in kubernets documentation:

https://kubernetes.io/docs/concepts/storage/storage-classes/#openstack-cinde... and I also made it default.

I did the following test: cinder volume created before hand and used in pod directly with the id, the volume is attached and mounted correctly like is described here: https://docs.openstack.org/magnum/latest/user/#storage

Now if I try to deploy wordpress using the first link or other helms that use volume claim, the volume is created automatically by kubernets but they are never attached or mounted to the instances.

On master I see the following error:

pv_protection_controller.go:116] PV pvc-48fed935-5b61-11e9-9901-fa163e5ebeae failed with : Operation cannot be fulfilled on persistentvolumes "pvc-48fed935-5b61-11e9-9901-fa163e5ebea> the object has been modified; please apply your changes to the latest version and try again

Is there something I miss? I'm using the wrong version of fedora-atomic? It's the latest version available for download.

I did find that someone else had this error but not with cinder: https://github.com/kubernetes/kubernetes/issues/72905