Red Hat Bugzilla – Bug 1471062
[RFE] etcd pod is in pending status due to pv is not created when deploying service catalog onto an existing cluster
Last modified: 2017-10-09 16:50:46 EDT
Description of problem:
On an existing cluster, enable service catalog deployment, at final, in openshift-ansible-service-broker project, asb and etcd pod are not running. due to no pv is created for etcd pvc.
Version-Release number of the following components:
Steps to Reproduce:
1. deploy a normal cluster
2. enable service catalog in inventory host file
3. deploy service catalog
# ansible-playbook -i inventory_file ./playbooks/byo/openshift-cluster/service-catalog.yml
4. playbook is finished successfully, go to openshift-ansible-service-broker project to check pod status.
# oc get po
NAME READY STATUS RESTARTS AGE
asb-281511082-q8s97 0/1 CrashLoopBackOff 14 54m
etcd-1487946270-46j9s 0/1 pending
# oc describe po etcd-1487946270-46j9s
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
1h 1h 53 default-scheduler Warning FailedScheduling SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "etcd", which is unexpected. (repeated 2 times)
1h 1h 1 default-scheduler Warning FailedScheduling no nodes available to schedule pods
1h 42m 124 default-scheduler Warning FailedScheduling SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "etcd", which is unexpected. (repeated 2 times)
# oc get pvc
NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE
etcd Pending 46m
# oc get pv
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
regpv-volume 17G RWX Retain Bound default/regpv-claim 1h
No etcd pv is created.
etcd pv is created created, and all pods are running well.
manually create etcd pv, pods are running well.
*** This bug has been marked as a duplicate of bug 1467574 ***
I do not think this bug is a dup of bug 1467574, the root cause of this bug is the following:
when running the separate service catalog playbook on an existing cluster, openshift_persistent_volumes is never called, so no pv is created. If running playbooks/byo/config.yml, no such issue.
While in BZ#1467574, it is running playbooks/byo/config.yml, but did not set openshift_hosted_etcd_storage to an existing nfs dir, want installer help create the nfs dir automatically. It is tracking installer does not create new nfs export dir on NFS server for etcd pv, the root cause is openshift_storage_nfs never take openshift_hosted_etcd_storage into consideration.
ok, depends on it then, we'll work on this post 3.6 GA
Need to add the persistent volumes playbooks from hosted into the service catalog playbook. Not going to get this for 3.6.1 but will be a 3.7 blocker.
Dropping priority/severity and marking it as a RFE (but keeping it under installer).
At this time a PV can be created and then the service_catalog.yml playbook can be run which would allow the etcd PVC to bind.