<div dir="ltr">To get the pod up and running, I have removed the threshold's parameters from the APB's deployment resource ->liveness and readinessProbes.<div><br></div><div>But I see this error now <div><br></div><div><div>time="2018-08-13T16:30:09Z" level=info msg="Broker successfully bootstrapped on startup"</div><div>time="2018-08-13T16:30:09Z" level=info msg="Listening on https://[::]:1338"</div><div>time="2018-08-13T16:30:09Z" level=info msg="Ansible Service Broker Starting"</div><div>ERROR: logging before flag.Parse: I0813 16:30:09.600491 1 serve.go:89] Serving securely on [::]:1338</div><div>time="2018-08-13T16:30:20Z" level=info msg="AnsibleBroker::Catalog"</div><div>time="2018-08-13T16:30:20Z" level=error msg="not adding spec dh-automation-broker-apb to list of services due to error transforming to service - Could not find the parameter type for: "</div><div>10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918</div><div>time="2018-08-13T16:30:40Z" level=info msg="AnsibleBroker::Catalog"</div><div>time="2018-08-13T16:30:40Z" level=error msg="not adding spec dh-automation-broker-apb to list of services due to error transforming to service - Could not find the parameter type for: "</div><div>10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918</div></div></div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px"><div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis <span dir="ltr"><<a href="mailto:gandrian@redhat.com" target="_blank">gandrian@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello,</div><div><br></div><div>I am seeing the same exact error as Charles under the same conditions -> installing ASB on Openshift Origin 3.10.</div><div><br></div><div>Regards<br></div></div><br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Thu, Aug 9, 2018 at 8:36 PM David Zager <<a href="mailto:dzager@redhat.com" target="_blank">dzager@redhat.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><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" target="_blank">`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" target="_blank">increased this from 15 seconds to 120</a>. I suspect that could be the cause.<div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon <<a href="mailto:jmontleo@redhat.com" target="_blank">jmontleo@redhat.com</a>> wrote:<br></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.<br>
<br>
Our downstream CI test are passing as of this morning using <br>
openshift-ansible with downstream images. From his gist logs it looked <br>
like the broker started, but I am not clear on what's happening to cause <br>
the getsockopt error.<br>
<br>
<a href="https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb" rel="noreferrer" target="_blank">https://gist.github.com/<wbr>cmoulliard/<wbr>716468a9e9beb21ba860806a30e3dd<wbr>cb</a><br>
<br>
It seems like the service name resolved, but it couldn't connect at the <br>
address "172.30.206.144". Perhaps there is a misconfiguration with the <br>
docker or openshift networking?<br>
<br>
On 08/09/2018 11:30 AM, John Matthews wrote:<br>
> +Jason/David who may be able to help<br>
> <br>
> <br>
> Hi Charles,<br>
> <br>
> "I don't see anymore the apb-etcd pod wuth openshift 3.10, it is normal ?"<br>
> <br>
> Yes, this is normal for 3.10, we moved to CRDs for the data we store, so <br>
> we dropped our own etcd and rely on regular k8s API.<br>
> <br>
> <br>
> "Error fetching catalog. Error getting broker catalog: <br>
> Gethttps://asb.openshift-<wbr>ansible-service-broker.svc:<wbr>1338/ansible-service-broker/<wbr>v2/catalog <br>
> <<a href="https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog" rel="noreferrer" target="_blank">https://asb.openshift-<wbr>ansible-service-broker.svc:<wbr>1338/ansible-service-broker/<wbr>v2/catalog</a>>: <br>
> 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: <br>
> no route to host"<br>
> <br>
> Please double check the namespace the automation broker is running in.<br>
> I wonder if there is a bug we missed with "openshift-ansible" deploying <br>
> with origin.<br>
> I believe the majority of our QE scenarios are with openshift-ansible <br>
> with downstream OCP or 'oc cluster up' with origin.<br>
> <br>
> Guessing, but perhaps there is a mismatch between actual namespace <br>
> broker is in versus what we are registering to service-catalog.<br>
> <br>
> <br>
> <br>
> <br>
> On Thu, Aug 9, 2018 at 4:29 AM, Charles Moulliard <<a href="mailto:cmoullia@redhat.com" target="_blank">cmoullia@redhat.com</a> <br>
> <mailto:<a href="mailto:cmoullia@redhat.com" target="_blank">cmoullia@redhat.com</a>>> wrote:<br>
> <br>
> Additional info. The ClusterServiceBroker reports this error<br>
> <br>
> Error fetching catalog. Error getting broker catalog: Get<br>
> <a href="https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog" rel="noreferrer" target="_blank">https://asb.openshift-<wbr>ansible-service-broker.svc:<wbr>1338/ansible-service-broker/<wbr>v2/catalog</a><br>
> <<a href="https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog" rel="noreferrer" target="_blank">https://asb.openshift-<wbr>ansible-service-broker.svc:<wbr>1338/ansible-service-broker/<wbr>v2/catalog</a>>:<br>
> 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>>:<br>
> getsockopt: no route to host<br>
> <br>
> On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard<br>
> <<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:<br>
> <br>
> Hi<br>
> <br>
> I can't install ASB on origin 3.10 anymore using the playbook<br>
> "openshift-ansible/playbooks/<wbr>openshift-service-catalog/<wbr>config.yml"<br>
> <br>
> The apb deployment starts, a pod is created and after x minutes<br>
> I see the status = "Failed" but the pod's log doesn't report ERROR<br>
> <br>
> Log :<br>
> <a href="https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb" rel="noreferrer" target="_blank">https://gist.github.com/<wbr>cmoulliard/<wbr>716468a9e9beb21ba860806a30e3dd<wbr>cb</a><br>
> <<a href="https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb" rel="noreferrer" target="_blank">https://gist.github.com/<wbr>cmoulliard/<wbr>716468a9e9beb21ba860806a30e3dd<wbr>cb</a>><br>
> <br>
> How can we troubleshoot and resolve such error ?<br>
> I don't see anymore the apb-etcd pod wuth openshift 3.10, it is<br>
> normal ?<br>
> <br>
> Regards<br>
> <br>
> Charles<br>
> <br>
> <br>
> <br>
> _____________________________<wbr>__________________<br>
> Ansible-service-broker mailing list<br>
> <a href="mailto:Ansible-service-broker@redhat.com" target="_blank">Ansible-service-broker@<wbr>redhat.com</a><br>
> <mailto:<a href="mailto:Ansible-service-broker@redhat.com" target="_blank">Ansible-service-<wbr>broker@redhat.com</a>><br>
> <a href="https://www.redhat.com/mailman/listinfo/ansible-service-broker" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/ansible-<wbr>service-broker</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/ansible-service-broker" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/ansible-<wbr>service-broker</a>><br>
> <br>
> <br>
<br>
-- <br>
Jason Montleon | email: <a href="mailto:jmontleo@redhat.com" target="_blank">jmontleo@redhat.com</a><br>
Software Engineer | gpg key: 0x069E3022<br>
Red Hat, Inc. | irc: jmontleo<br>
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><br>
</blockquote></div>
______________________________<wbr>_________________<br>
Ansible-service-broker mailing list<br>
<a href="mailto:Ansible-service-broker@redhat.com" target="_blank">Ansible-service-broker@redhat.<wbr>com</a><br>
</div></div><a href="https://www.redhat.com/mailman/listinfo/ansible-service-broker" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/ansible-<wbr>service-broker</a><br>
</blockquote></div>
</blockquote></div><br></div></div>