My pod for openshift-ansible-service-broker is failing to start, with
this error found in the logs:
Using config file mounted to /etc/ansible-service-broker/config.yaml
============================================================
== Starting Ansible Service Broker... ==
============================================================
[2018-07-20T13:01:06.151Z] [NOTICE] Initializing clients...
[2018-07-20T13:01:06.152Z] [INFO] == ETCD CX ==
[2018-07-20T13:01:06.152Z] [INFO] EtcdHost:
asb-etcd.openshift-ansible-service-broker.svc
[2018-07-20T13:01:06.152Z] [INFO] EtcdPort: 2379
[2018-07-20T13:01:06.152Z] [INFO] Endpoints:
[https://asb-etcd.openshift-ansible-service-broker.svc:2379 ]
[2018-07-20T13:01:06.178Z] [ERROR] client: etcd cluster is unavailable
or misconfigured; error #0: x509: certificate signed by unknown authority
The pod for asb-etcd is running fine, but in the logs I see these errors:
2018-07-20 12:27:45.723585 I | embed: rejected connection from
"10.129.4.1:32916" (error "remote error: tls: bad certificate",
ServerName "asb-etcd.openshift-ansible-service-broker.svc")
This pod used to be running fine, but now won't start. Possibly this is
related to pushing out updated certificates using the
redeploy-certificates.yml playbook.
Any ideas on how to resolve this?
Or maybe to undeploy and redeploy the OAB?
This is using Origin 3.7.2
Thanks
Tim
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
