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
Contrail fails to successfully deploy with the Helm chart due to mismatch volume names. The Contrail pods seem to be looking for the configMapcontrail-kube-manager-token instead of a random generated secretNamecontrail-kube-manager-token-m1tjr.
I'm running a three node Kubernetes cluster with OpenStack-Helm.
Contrail R4.1 (same with R4.0)
Kubernetes v1.7.5
Helm v2.6.1
root@k8s-node1:/tmp/tmp.SB1UVbuRMJ/contrail-docker/kubernetes/helm/contrail# helm install --name contrail .
root@k8s-node1:/tmp/tmp.SB1UVbuRMJ/contrail-docker/kubernetes/helm/contrail# kubectl -n kube-system describe pod contrail-kube-manager-mxs7w
Name: contrail-kube-manager-mxs7w
Namespace: kube-system
Node: k8s-node1/10.100.0.3
Start Time: Tue, 17 Oct 2017 13:33:39 +0000
Labels: app=contrail-cni
contrail_function=contrail-kube-manager
controller-revision-hash=3793872802
pod-template-generation=1
Annotations: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"DaemonSet","namespace":"kube-system","name":"contrail-kube-manager","uid":"c887f36f-b33f-11e7-9794-fa163e2...
Status: Pending
IP: 10.100.0.3
Created By: DaemonSet/contrail-kube-manager
Controlled By: DaemonSet/contrail-kube-manager
Containers:
contrail-kube-manager:
Container ID:
Image: docker.io/opencontrail/contrail-kube-manager-ubuntu16.04:4.0.1.0
Image ID:
Port: <none>
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/tmp/contrailctl from contrailctl-kube-manager (rw)
/tmp/serviceaccount from pod-secret (rw)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
contrailctl-kube-manager:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: contrailctl-config
Optional: false
pod-secret:
Type: Secret (a volume populated by a Secret)
SecretName: contrail-kube-manager-token
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node-role.kubernetes.io/master:NoSchedule
node.alpha.kubernetes.io/notReady:NoExecute
node.alpha.kubernetes.io/unreachable:NoExecute
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
22m 22m 1 kubelet, k8s-node1 Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "contrailctl-kube-manager"
20m 2m 9 kubelet, k8s-node1 Warning FailedMount Unable to mount volumes for pod "contrail-kube-manager-mxs7w_kube-system(c8c114f5-b33f-11e7-9794-fa163e23bfa5)": timeout expired waiting for volumes to attach/mount for pod "kube-system"/"contrail-kube-manager-mxs7w". list of unattached/unmounted volumes=[pod-secret]
20m 2m 9 kubelet, k8s-node1 Warning FailedSync Error syncing pod
22m 1m 18 kubelet, k8s-node1 Warning FailedMount MountVolume.SetUp failed for volume "pod-secret" : secrets "contrail-kube-manager-token" not found
root@k8s-node1:/tmp/tmp.SB1UVbuRMJ/contrail-docker/kubernetes/helm/contrail# kubectl -n kube-system get secrets |grep contrail
contrail-kube-manager-token-m1tjr kubernetes.io/service-account-token 3 22m
The text was updated successfully, but these errors were encountered:
Contrail fails to successfully deploy with the Helm chart due to mismatch volume names. The Contrail pods seem to be looking for the configMap
contrail-kube-manager-token
instead of a random generated secretNamecontrail-kube-manager-token-m1tjr
.I'm running a three node Kubernetes cluster with OpenStack-Helm.
The text was updated successfully, but these errors were encountered: