Bug 1520291
| Summary: | ASB pods were in error status after installation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gaoyun Pei <gpei> |
| Component: | Installer | Assignee: | Fabian von Feilitzsch <fabian> |
| Status: | CLOSED NOTABUG | QA Contact: | Gaoyun Pei <gpei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.7.1 | CC: | aos-bugs, gpei, jokerman, jpeeler, mark.vinkx, mmccomas, qixuan.wang, wmeng |
| Target Milestone: | --- | ||
| Target Release: | 3.7.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-24 15:18:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gaoyun Pei
2017-12-04 08:17:59 UTC
If no PV is defined then the broker will be unable to start. It looks like you set up NFS backing for the registry PV, you can do the same for the broker PV by adding these options to your inventory (as documented in https://docs.openshift.org/latest/install_config/install/advanced_install.html#configuring-openshift-ansible-broker) openshift_hosted_etcd_storage_kind=nfs openshift_hosted_etcd_storage_nfs_options="*(rw,root_squash,sync,no_wdelay)" openshift_hosted_etcd_storage_nfs_directory=/opt/osev3-etcd openshift_hosted_etcd_storage_volume_name=etcd-vol2 openshift_hosted_etcd_storage_access_modes=["ReadWriteOnce"] openshift_hosted_etcd_storage_volume_size=1G openshift_hosted_etcd_storage_labels={'storage': 'etcd'} Does this fix the issue or was there something additional that I missed? Thanks Fabian! After adding the openshift_hosted_etcd_storage_* related options, the required pv for ansible-service-broker was created, and asb pods are running well. The openshift-ansible version I used is openshift-ansible-3.7.26-1.git.0.f87f1af.el7.noarch.rpm. So my thinking is now we're installing ASB by default no matter user want it or not, maybe we could add a clear prompt when user didn't set correct PV options for it? Just like what I have done, I didn't know I have to set openshift_hosted_etcd_storage_* options when installing an ocp-3.7 cluster without cloudprovider enabled. I'll appreciate it very much if installer could give some hint in this case. Thanks! Hi there, I ran into the same problem with OCP 3.9.14 deployed on OpenStack + Glusterfs, there is storageclass, then how should I configure openshift_hosted_etcd_storage_* options? Thanks! [root@host-172-16-120-146 ~]# oc describe pvc Name: etcd Namespace: openshift-ansible-service-broker StorageClass: Status: Pending Volume: Labels: <none> Annotations: <none> Finalizers: [] Capacity: Access Modes: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal FailedBinding 2m (x26 over 8m) persistentvolume-controller no persistent volumes available for this claim and no storage class is set [root@host-172-16-120-146 ~]# oc get pv No resources found. [root@host-172-16-120-146 ~]# oc describe storageclass Name: glusterfs-storage IsDefaultClass: No Annotations: <none> Provisioner: kubernetes.io/glusterfs Parameters: resturl=http://heketi-storage-glusterfs.apps.0416-2iv.qe.rhcloud.com,restuser=admin,secretName=heketi-storage-admin-secret,secretNamespace=glusterfs ReclaimPolicy: Delete Events: <none> Hi there, I enabled the cloud provider to avoid the problem. Hey, did that resolve your issue or is there still work we need to do here? I think it would be difficult to automatically detect incorrect PV settings due to the large number of possible setups, particularly in the case of an upgrade or the broker being added to an existing cluster. The dependence on the PV is in the documentation, and is going away in v3.10, so I think we can go ahead and close this unless you have an objection. Closing for now, if you feel like this issue needs additional work feel free to reopen. Hi Fabian, sorry for the late reply. Comment 8 makes sense, let's close it. |