Issue:
Persistent volume claim remains in “Pending” status.
PVC message states “waiting for a volume to be created”
Trrace logs on unit-openstack-integrator-0 looks like normal operation but no mention of a provisioning attempt failure or request.
k8s functions in all other respects.
Details:
Charmed-Kubernetes implementation on OpenStack
OpenStack 5.2.0 Stein
cs:~containers/openstack-integrator-59 (trust: true)
cs:~containers/kubernetes-master-826
cs:~containers/kubernetes-worker-661
Relations:
- - openstack-integrator:clients
- kubernetes-master:openstack
- - openstack-integrator:clients
- kubernetes-worker:openstack
Any help would be greatly appreciated.
How did you deploy openstack ?
Paul, thanks for reply. I have been doing further investigation and this may not be related to the openstack-integrator directly. I will investigate further before progressing this as to not wast everyone’s time.
Further digging provides this message in the openstack-cloud-controller-manager pod.
I0605 04:15:34.989241 1 serving.go:312] Generated self-signed cert in-memory
W0605 04:15:35.394752 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: “client-ca::kube-system::extension-apiserver-authentication::client-ca-file” due to: configmap “extension-apiserver-authentication” not found
W0605 04:15:35.394816 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: “client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file” due to: configmap “extension-apiserver-authentication” not found
W0605 04:15:35.406132 1 client_config.go:543] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0605 04:15:35.408272 1 controllermanager.go:120] Version: v0.0.0-master+$Format:%h$
W0605 04:15:35.408311 1 plugins.go:115] WARNING: openstack built-in cloud provider is now deprecated. Please use ‘external’ cloud provider for openstack: https://github.com/kubernetes/cloud-provider-openstack
I0605 04:15:35.603529 1 openstack.go:261] New openstack client created failed with config
I checked the cloud.conf setting in the k8s Secret and it appears to have all the correct key = value information.
[Global]
auth-url = #####
region = #####
username = #####
password = #####
tenant-name = #####
domain-name = #####
[LoadBalancer]
lb-method = ROUND_ROBIN
Will continue to investigate but if anyone can shed some light it would be appreciated.