| 2020-03-23 14:11:32 |
Barry Price |
description |
After deploying the integrator to a cluster, 'juju status' suggests all is well:
App Version Status Scale Charm Store Rev OS Notes
openstack-integrator train active 1 openstack-integrator local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
openstack-integrator/0* active idle 13 10.15.210.18 Ready
And the storage class certainly shows up:
$ kubectl get sc --all-namespaces
NAME PROVISIONER AGE
cdk-cinder csi-cinderplugin 9d
But on closer inspection:
$ kubectl get po --all-namespaces | grep csi-cinder
kube-system csi-cinder-controllerplugin-0 2/4 CrashLoopBackOff 1300 45h
kube-system csi-cinder-nodeplugin-p6lzs 1/2 CrashLoopBackOff 3391 9d
kube-system csi-cinder-nodeplugin-schgg 1/2 CrashLoopBackOff 2622 9d
Is it possible (and if so, is it a good idea) for the charm to notice that the pods haven't started, and adjust application status to e.g. "blocked"? |
After deploying the integrator to a cluster, 'juju status' suggests all is well:
App Version Status Scale Charm Store Rev OS Notes
openstack-integrator train active 1 openstack-integrator local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
openstack-integrator/0* active idle 13 10.15.210.18 Ready
And the storage class certainly shows up:
$ kubectl get sc --all-namespaces
NAME PROVISIONER AGE
cdk-cinder csi-cinderplugin 9d
But on closer inspection:
$ kubectl get po --all-namespaces | grep csi-cinder
kube-system csi-cinder-controllerplugin-0 2/4 CrashLoopBackOff 1300 45h
kube-system csi-cinder-nodeplugin-p6lzs 1/2 CrashLoopBackOff 3391 9d
kube-system csi-cinder-nodeplugin-schgg 1/2 CrashLoopBackOff 2622 9d
See LP:1868368 for the above issue itself, but is it possible (and if so, is it a good idea) for the charm to notice that the pods haven't started, and adjust application status to e.g. "blocked"? |
|
