Ask Your Question

cinder pods in init state when deployed with openstack-helm

asked 2020-02-14 10:03:51 -0600

sanjay khuntia gravatar image

Hi all, I have created a k8s cluster with total 4 nodes - 1st node for k8s master, 2nd is controller and rest 2 are computes. I am able to successfully deploy following openstack-helm charts in my cluster using "helm install service local/service -n openstack" command. mariadb rabbitmq memcached ingress keystone and glance

kubectl get pods -n openstack
NAME                                          READY   STATUS      RESTARTS   AGE
cinder-api-6f55567d8f-cb4lr                   0/1     Init:0/2    0          3h13m
cinder-backup-7c5947c49c-978pr                0/1     Init:0/3    0          3h13m
cinder-backup-storage-init-422d8              0/1     Completed   0          3h13m
cinder-bootstrap-cn8nm                        0/1     Init:0/1    0          3h13m
cinder-create-internal-tenant-snr9b           0/1     Completed   0          3h13m
cinder-db-init-s4fs9                          0/1     Completed   0          3h13m
cinder-db-sync-n6ckd                          0/1     Completed   0          3h13m
cinder-ks-endpoints-dxrvr                     0/9     Completed   2          3h13m
cinder-ks-service-sh66k                       0/3     Completed   0          3h13m
cinder-ks-user-9wm5m                          0/1     Completed   1          3h13m
cinder-rabbit-init-t9m79                      0/1     Completed   0          3h13m
cinder-scheduler-578d976c69-q94ft             0/1     Init:0/2    0          3h13m
cinder-storage-init-9zfcf                     0/1     Init:0/2    0          3h13m
cinder-volume-7ddfb99bfb-crl4g                0/1     Init:0/4    0          3h13m
cinder-volume-usage-audit-1581683700-7ff9r    0/1     Init:0/1    0          3h11m
glance-api-54cb8645c8-7v577                   1/1     Running     0          3d
glance-bootstrap-59sb7                        0/1     Completed   3          3d
glance-db-init-sfqhd                          0/1     Completed   0          3d
glance-db-sync-zcn7n                          0/1     Completed   0          3d
glance-ks-endpoints-n6ddw                     0/3     Completed   0          3d
glance-ks-service-bdxcp                       0/1     Completed   0          3d
glance-ks-user-n7nms                          0/1     Completed   0          3d
glance-metadefs-load-z9prl                    0/1     Completed   0          3d
glance-rabbit-init-cjffk                      0/1     Completed   0          3d
glance-storage-init-8kssq                     0/1     Completed   0          3d
ingress-8f98f7d96-q4bjp                       1/1     Running     0          3d
ingress-error-pages-84647d8fcb-9b5bz          1/1     Running     0          3d
keystone-api-5785f4787-fwvhq                  1/1     Running     0          3d3h
keystone-bootstrap-rlcdn                      0/1     Completed   0          3d3h
keystone-credential-setup-d7jj6               0/1     Completed   0          3d3h
keystone-db-init-xg66h                        0/1     Completed   0          3d3h
keystone-db-sync-x6d66                        0/1     Completed   0          3d3h
keystone-domain-manage-l5snm                  0/1     Completed   0          3d3h
keystone-fernet-rotate-1581595200-5t6lw       0/1     Completed   0          27h
keystone-fernet-rotate-1581638400-9c796       0/1     Completed   0          15h
keystone-fernet-rotate-1581681600-fwsfn       0/1     Completed   0          3h45m
keystone-fernet-setup-9f2lj                   0/1     Completed   0          3d3h
keystone-rabbit-init-jbv6t                    0/1     Completed   0          3d3h
mariadb-ingress-669c67b6b5-cd8pt              1/1     Running     0          4d8h
mariadb-ingress-669c67b6b5-k7jkn              1/1     Running     0          4d8h
mariadb-ingress-error-pages-d77467d69-8xqxs   1/1     Running     0          4d8h
mariadb-server-0                              1/1     Running     0          4d8h
memcached-memcached-7b49f48865-jw6cp          1/1     Running     0          3d3h
rabbitmq-cluster-wait-wfw4s                   0/1     Completed   0          3d4h
rabbitmq-rabbitmq-0                           1/1     Running     0          3d4h

I need to use persistent volume (pv) as my cinder storage for which I have created PV and PVC for cinder before deploying cinder using helm.

stack@k8s-cluster-vm1:~$ kubectl get pv -n openstack
NAME              CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                         STORAGECLASS   REASON   AGE
local-pv          5Gi        RWO            Retain           Bound    openstack/mysql-data-mariadb-server-0         general                 4d8h
local-pv-glance   10Gi       RWO            Retain           Bound    openstack/glance-images                       general                 3d1h
local-pvcinder    5Gi        RWO            Retain           Bound    openstack/cinder-backup                       general                 3h29m
local-rabbitpv    5Gi        RWO            Retain           Bound    openstack/rabbitmq-data-rabbitmq-rabbitmq-0   general                 3d5h
stack@k8s-cluster-vm1:~$ kubectl get pvc -n openstack
NAME                                STATUS   VOLUME            CAPACITY   ACCESS MODES   STORAGECLASS   AGE
cinder-backup                       Bound    local-pvcinder    5Gi        RWO            general        3h30m
glance-images                       Bound    local-pv-glance   10Gi       RWO            general        3d
mysql-data-mariadb-server-0         Bound    local-pv          5Gi        RWO            general        4d8h
rabbitmq-data-rabbitmq-rabbitmq-0   Bound    local-rabbitpv    5Gi        RWO            general        3d5h

stack@k8s-cluster-vm1:~$ kubectl get nodes -n openstack
NAME                STATUS   ROLES    AGE    VERSION
k8s-cluster-vm1   Ready    master   6d4h   v1.17.0
k8s-cluster-vm2   Ready    <none>   6d4h   v1.17.0
k8s-cluster-vm3   Ready    <none>   6d4h ...
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2020-02-24 08:32:12 -0600

sanjay khuntia gravatar image

Got a reply from Openstack-helm developer community that cinder has no support for NFS provisioning in helm.



edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2020-02-14 10:03:51 -0600

Seen: 59 times

Last updated: 13 hours ago