You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
What happened:
I got following error message from kube-controll-manager when I claim persistent volume.
Then kubectl get pvc show state pending.
$ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
pv1 Pending cinder 8m26s
# /var/vcap/sys/logs/kube-controller-managerkube-controller-manager.stderr.log
I0819 07:44:17.682405 1 event.go:209] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"pv1", UID:"22206f4b-c255-11e9-bda3-fa163e1bf5e1", APIVersion:"v1", ResourceVersion:"4537964", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' Failed to provision volume with StorageClass "cinder": OpenStack cloud provider was not initialized properly : stat /etc/kubernetes/cloud-config: no such file or directory
What you expected to happen:
When execute kubectl apply -f manifest.yml, openstack cinder should be provisioning volume properly and attached to the pod.
How to reproduce it (as minimally and precisely as possible):
What happened:
I got following error message from kube-controll-manager when I claim persistent volume.
Then
kubectl get pvc
show state pending.then my manifest is:
and I configured storage class.
What you expected to happen:
When execute
kubectl apply -f manifest.yml
, openstack cinder should be provisioning volume properly and attached to the pod.How to reproduce it (as minimally and precisely as possible):
1
kubectrl apply -f storage-class.yml
1
kubectrl apply -f manifest.yml
Anything else we need to know?:
Environment:
bosh -d <deployment> deployment
):kubo-deployment v0.34.0
bosh -e <environment> environment
):kubectl version
):aws
,gcp
,vsphere
):Openstack - mitaka
The text was updated successfully, but these errors were encountered: