-
Notifications
You must be signed in to change notification settings - Fork 94
Description
I am doing hyperledger on kubernetes.I am doing it by kubeadm.I have run this python3.5 transform/run.py command and check my pods.They are not able to come in running stage.Always status is like following
org1 ca-f555d76c9-m4mmr 0/1 ContainerCreating 0 11m
org1 cli-55b9bbc455-dkgb2 0/1 ContainerCreating 0 11m
org1 peer0-org1-54c495c896-pzpdl 0/2 ContainerCreating 0 11m
org1 peer1-org1-89594585-g4dmz 0/2 ContainerCreating 0 11m
org2 ca-56c6d75565-wmf8b 0/1 ContainerCreating 0 11m
org2 cli-77c79d8fcd-q7nk5 0/1 ContainerCreating 0 11m
org2 peer0-org2-5d6cd4655-mdnwq 0/2 ContainerCreating 0 11m
org2 peer1-org2-6696fc8cb6-5jrrp 0/2 ContainerCreating 0 11m
orgorderer1 orderer0-orgorderer1-7748df7fd7-nndvt 0/1 ContainerCreating 0 11m
For investigation,I have run kubectl -n org1 describe pods command.I saw an error like this
Events:
Type Reason Age From Message
Normal Scheduled 6m default-scheduler Successfully assigned peer1-org2-6696fc8cb6-5jrrp to dell-latitude-e6420
Normal SuccessfulMountVolume 6m kubelet, dell-latitude-e6420 MountVolume.SetUp succeeded for volume "run"
Normal SuccessfulMountVolume 6m kubelet, dell-latitude-e6420 MountVolume.SetUp succeeded for volume "default-token-66zhx"
Warning FailedMount 2m (x2 over 4m) kubelet, dell-latitude-e6420 Unable to mount volumes for pod "peer1-org2-6696fc8cb6-5jrrp_org2(98d2826f-07e8-11e8-923d-d4bed90fb136)": timeout expired waiting for volumes to attach/mount for pod "org2"/"peer1-org2-6696fc8cb6-5jrrp". list of unattached/unmounted volumes=[certificate]
Can you please look into it?