<div dir="ltr">After reading through the logs and seeing the way the cut off, I'm curious if it's related to the <a href="https://github.com/openshift/openshift-ansible/blob/master/roles/ansible_service_broker/templates/asb_dc.yaml.j2#L59-L72">`initialDelaySeconds` in the broker's deployment config</a>. With the upstream broker-apb we <a href="https://github.com/openshift/ansible-service-broker/blob/master/apb/defaults/main.yml#L17">increased this from 15 seconds to 120</a>. I suspect that could be the cause.<div> </div></div> <div class="gmail_quote"><div dir="ltr">On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon <<a href="mailto:jmontleo@redhat.com">jmontleo@redhat.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I made some comments in irc this morning. Our downstream CI test are passing as of this morning using openshift-ansible with downstream images. From his gist logs it looked like the broker started, but I am not clear on what's happening to cause the getsockopt error. <a href="https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb" rel="noreferrer" target="_blank">https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb</a> It seems like the service name resolved, but it couldn't connect at the address "172.30.206.144". Perhaps there is a misconfiguration with the docker or openshift networking? On 08/09/2018 11:30 AM, John Matthews wrote: > +Jason/David who may be able to help > > > Hi Charles, > > "I don't see anymore the apb-etcd pod wuth openshift 3.10, it is normal ?" > > Yes, this is normal for 3.10, we moved to CRDs for the data we store, so > we dropped our own etcd and rely on regular k8s API. > > > "Error fetching catalog. Error getting broker catalog: > Gethttps://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > <<a href="https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog" rel="noreferrer" target="_blank">https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog</a>>: > dial tcp172.30.206.144:1338 <<a href="http://172.30.206.144:1338/" rel="noreferrer" target="_blank">http://172.30.206.144:1338/</a>>: getsockopt: > no route to host" > > Please double check the namespace the automation broker is running in. > I wonder if there is a bug we missed with "openshift-ansible" deploying > with origin. > I believe the majority of our QE scenarios are with openshift-ansible > with downstream OCP or 'oc cluster up' with origin. > > Guessing, but perhaps there is a mismatch between actual namespace > broker is in versus what we are registering to service-catalog. > > > > > On Thu, Aug 9, 2018 at 4:29 AM, Charles Moulliard <<a href="mailto:cmoullia@redhat.com" target="_blank">cmoullia@redhat.com</a> > <mailto:<a href="mailto:cmoullia@redhat.com" target="_blank">cmoullia@redhat.com</a>>> wrote: > > Additional info. The ClusterServiceBroker reports this error > > Error fetching catalog. Error getting broker catalog: Get > <a href="https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog" rel="noreferrer" target="_blank">https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog</a> > <<a href="https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog" rel="noreferrer" target="_blank">https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog</a>>: > dial tcp <a href="http://172.30.206.144:1338" rel="noreferrer" target="_blank">172.30.206.144:1338</a> <<a href="http://172.30.206.144:1338" rel="noreferrer" target="_blank">http://172.30.206.144:1338</a>>: > getsockopt: no route to host > > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard > <<a href="mailto:cmoullia@redhat.com" target="_blank">cmoullia@redhat.com</a> <mailto:<a href="mailto:cmoullia@redhat.com" target="_blank">cmoullia@redhat.com</a>>> wrote: > > Hi > > I can't install ASB on origin 3.10 anymore using the playbook > "openshift-ansible/playbooks/openshift-service-catalog/config.yml" > > The apb deployment starts, a pod is created and after x minutes > I see the status = "Failed" but the pod's log doesn't report ERROR > > Log : > <a href="https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb" rel="noreferrer" target="_blank">https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb</a> > <<a href="https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb" rel="noreferrer" target="_blank">https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb</a>> > > How can we troubleshoot and resolve such error ? > I don't see anymore the apb-etcd pod wuth openshift 3.10, it is > normal ? > > Regards > > Charles > > > > _______________________________________________ > Ansible-service-broker mailing list > <a href="mailto:Ansible-service-broker@redhat.com" target="_blank">Ansible-service-broker@redhat.com</a> > <mailto:<a href="mailto:Ansible-service-broker@redhat.com" target="_blank">Ansible-service-broker@redhat.com</a>> > <a href="https://www.redhat.com/mailman/listinfo/ansible-service-broker" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/ansible-service-broker</a> > <<a href="https://www.redhat.com/mailman/listinfo/ansible-service-broker" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/ansible-service-broker</a>> > > -- Jason Montleon | email: <a href="mailto:jmontleo@redhat.com" target="_blank">jmontleo@redhat.com</a> Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: <a href="tel:(978)%20392-3930" value="+19783923930" target="_blank">978-392-3930</a> | cell: <a href="tel:(508)%20496-0663" value="+15084960663" target="_blank">508-496-0663</a> </blockquote></div>