From jesusr at redhat.com Tue Aug 7 14:18:37 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 07 Aug 2018 10:18:37 -0400 Subject: [Ansible-service-broker] Automation Broker Community Meeting Aug 7, 2018 Message-ID: <0381998cd5224fe77c4a40afc61e86a4bb9c756b.camel@redhat.com> ========================================================== #asbroker: Automation Broker Community Meeting Aug 7, 2018 ========================================================== Meeting started by jmrodri at 13:32:58 UTC. The full logs are available at asbroker/2018/asbroker.2018-08-07-13.32.log.html . Meeting summary --------------- * attendance (jmrodri, 13:33:07) * News (jmrodri, 13:37:12) * bundle-lib 0.2.7 released July 27th (jmrodri, 13:38:37) * LINK: https://github.com/automationbroker/bundle-lib/releases/tag/0.2.7 (jmrodri, 13:38:41) * automation broker build 1.3.7-1 was done yesterday (jmrodri, 13:39:46) * Preview Actions (jmrodri, 13:40:20) * jmrodri to test issue 941 (jmrodri, 13:40:35) * LINK: https://github.com/openshift/ansible-service-broker/issues/941 (jmrodri, 13:40:45) * shurley write up brief comment on issue 111 (jmrodri, 13:42:10) * LINK: https://github.com/automationbroker/bundle-lib/issues/111 (jmrodri, 13:42:19) * ernelson investigate issue 974, close if not a broker issue (jmrodri, 13:43:53) * LINK: https://github.com/openshift/ansible-service-broker/issues/974 (jmrodri, 13:44:04) * LINK: https://github.com/openshift/ansible-service-broker/issues/974 (jmrodri, 13:44:09) * dzager to update and close out issue 853 (jmrodri, 13:44:52) * LINK: https://github.com/openshift/ansible-service-broker/issues/853 (jmrodri, 13:45:00) * jmrodri determine if 470 needs to remain open (jmrodri, 13:45:54) * LINK: https://github.com/openshift/ansible-service-broker/issues/470 (jmrodri, 13:46:00) * ACTION: jmrodri determine if issue 470 is still an issue https://github.com/openshift/ansible-service-broker/issues/470 (jmrodri, 13:46:13) * Bugs/Issue triage (jmrodri, 13:46:28) * bundle-lib issues (jmrodri, 13:46:36) * automation broker (jmrodri, 13:46:55) * 2 new issues were created (jmrodri, 13:47:18) * Failed provision will automatically trigger continous deprovision (jmrodri, 13:47:55) * LINK: https://github.com/openshift/ansible-service-broker/issues/1010 (jmrodri, 13:48:01) * ACTION: jmrodri add notes from this irc discussion to issue 1010 https://github.com/openshift/ansible-service-broker/issues/1010 (jmrodri, 13:56:14) * Multiline secrets are not correctly parsed (jmrodri, 13:56:34) * LINK: https://github.com/openshift/ansible-service-broker/issues/1028 (jmrodri, 13:56:40) * ACTION: jmrodri assign issue 1028 to someone https://github.com/openshift/ansible-service-broker/issues/1028 (jmrodri, 13:58:56) * 5 release 1.3 issues open (jmrodri, 13:59:24) * LINK: https://github.com/openshift/ansible-service-broker/issues?q=is%3Aissue+is%3Aopen+label%3A%223.11+%7C+release-1.3%22 (jmrodri, 13:59:27) * ACTION: ernelson get an answer on issue 974 (jmrodri, 14:00:25) * open discussion (jmrodri, 14:02:30) * consider making this IRC meeting bi-weekly or monthly (jmrodri, 14:02:41) * ACTION: jmrodri update meeting invite to be bi-weekly, send out email to asb list to announce it (jmrodri, 14:04:56) * ACTION: jmrodri send out meeting minutes for today (jmrodri, 14:05:05) Meeting ended at 14:07:28 UTC. Action Items ------------ * jmrodri determine if issue 470 is still an issue https://github.com/openshift/ansible-service-broker/issues/470 * jmrodri add notes from this irc discussion to issue 1010 https://github.com/openshift/ansible-service-broker/issues/1010 * jmrodri assign issue 1028 to someone https://github.com/openshift/ansible-service-broker/issues/1028 * ernelson get an answer on issue 974 * jmrodri update meeting invite to be bi-weekly, send out email to asb list to announce it * jmrodri send out meeting minutes for today Action Items, by person ----------------------- * ernelson * ernelson get an answer on issue 974 * jmrodri * jmrodri determine if issue 470 is still an issue https://github.com/openshift/ansible-service-broker/issues/470 * jmrodri add notes from this irc discussion to issue 1010 https://github.com/openshift/ansible-service-broker/issues/1010 * jmrodri assign issue 1028 to someone https://github.com/openshift/ansible-service-broker/issues/1028 * jmrodri update meeting invite to be bi-weekly, send out email to asb list to announce it * jmrodri send out meeting minutes for today * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jmrodri (89) * brokerbot (38) * ernelson (13) * dzager (7) * dymurray (6) * matzew (2) * jmontleon (2) * darkmagic (1) * dwhatley (1) * mhrivnak (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From jesusr at redhat.com Wed Aug 8 15:52:18 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Wed, 08 Aug 2018 11:52:18 -0400 Subject: [Ansible-service-broker] Change to Automation Broker IRC meeting Message-ID: <58eff7a226d4ea27732859511e34526575a53598.camel@redhat.com> At the August 7th, 2018 Automation Broker IRC meeting, we discussed changing the frequency of the meetings from weekly to bi-weekly. We will meeting the first and third Tuesday of the month. The next meeting will be Tuesday August 21st. Followed by Sept 4th, and Sept 18th. I will update the calendar invite this week. Sincerely, jesus -- jesus m. rodriguez | jesusr at redhat.com principal software engineer | irc: zeus red hat systems management | 919.754.4413 (w) rhce # 805008586930012 | 919.623.0080 (c) +---------------------------------------------+ | "you will be assimilated; | | resistance is futile" | | -- Borg | +---------------------------------------------+ From cmoullia at redhat.com Thu Aug 9 08:22:26 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 9 Aug 2018 10:22:26 +0200 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 Message-ID: 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 : https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Thu Aug 9 08:29:05 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 9 Aug 2018 10:29:05 +0200 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: Additional info. The ClusterServiceBroker reports this error Error fetching catalog. Error getting broker catalog: Get https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog: dial tcp 172.30.206.144:1338: getsockopt: no route to host On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard 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 : https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmatthew at redhat.com Thu Aug 9 15:30:33 2018 From: jmatthew at redhat.com (John Matthews) Date: Thu, 9 Aug 2018 11:30:33 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: +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: Get https://asb.openshift-ansible-service-broker.svc:1338/ ansible-service-broker/v2/catalog: dial tcp 172.30.206.144:1338: 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 wrote: > Additional info. The ClusterServiceBroker reports this error > > Error fetching catalog. Error getting broker catalog: Get > https://asb.openshift-ansible-service-broker.svc:1338/ > ansible-service-broker/v2/catalog: dial tcp 172.30.206.144:1338: > getsockopt: no route to host > > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard > 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 : https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >> >> 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 > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmontleo at redhat.com Thu Aug 9 15:37:42 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Thu, 9 Aug 2018 11:37:42 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: 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. https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb 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 > : > dial tcp172.30.206.144:1338 : 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 > wrote: > > Additional info. The ClusterServiceBroker reports this error > > Error fetching catalog. Error getting broker catalog: Get > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > : > dial tcp 172.30.206.144:1338 : > getsockopt: no route to host > > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard > > 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 : > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > 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 > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From dzager at redhat.com Thu Aug 9 17:36:11 2018 From: dzager at redhat.com (David Zager) Date: Thu, 9 Aug 2018 13:36:11 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: After reading through the logs and seeing the way the cut off, I'm curious if it's related to the `initialDelaySeconds` in the broker's deployment config . With the upstream broker-apb we increased this from 15 seconds to 120 . I suspect that could be the cause. On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon wrote: > 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. > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > 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 > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog>: > > > dial tcp172.30.206.144:1338 : 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 > > wrote: > > > > Additional info. The ClusterServiceBroker reports this error > > > > Error fetching catalog. Error getting broker catalog: Get > > > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >: > > dial tcp 172.30.206.144:1338 : > > getsockopt: no route to host > > > > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard > > > 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 : > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> > > > > 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 > > Ansible-service-broker at redhat.com > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > > -- > Jason Montleon | email: jmontleo at redhat.com > Software Engineer | gpg key: 0x069E3022 > Red Hat, Inc. | irc: jmontleo > desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 > <(508)%20496-0663> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gandrian at redhat.com Fri Aug 10 06:31:58 2018 From: gandrian at redhat.com (Georgios Andrianakis) Date: Fri, 10 Aug 2018 09:31:58 +0300 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: Hello, I am seeing the same exact error as Charles under the same conditions -> installing ASB on Openshift Origin 3.10. Regards On Thu, Aug 9, 2018 at 8:36 PM David Zager wrote: > After reading through the logs and seeing the way the cut off, I'm curious > if it's related to the `initialDelaySeconds` in the broker's deployment > config > . > With the upstream broker-apb we increased this from 15 seconds to 120 > . > I suspect that could be the cause. > > > On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon > wrote: > >> 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. >> >> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >> >> 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 >> >> > < >> https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog>: >> >> > dial tcp172.30.206.144:1338 : 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 > > > wrote: >> > >> > Additional info. The ClusterServiceBroker reports this error >> > >> > Error fetching catalog. Error getting broker catalog: Get >> > >> https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog >> > < >> https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog >> >: >> > dial tcp 172.30.206.144:1338 : >> > getsockopt: no route to host >> > >> > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard >> > > 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 : >> > >> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >> > < >> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> >> > >> > 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 >> > Ansible-service-broker at redhat.com >> > >> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> > >> > >> >> -- >> Jason Montleon | email: jmontleo at redhat.com >> Software Engineer | gpg key: 0x069E3022 >> Red Hat, Inc. | irc: jmontleo >> desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 >> <(508)%20496-0663> >> > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Aug 13 16:35:14 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 13 Aug 2018 18:35:14 +0200 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: To get the pod up and running, I have removed the threshold's parameters from the APB's deployment resource ->liveness and readinessProbes. But I see this error now time="2018-08-13T16:30:09Z" level=info msg="Broker successfully bootstrapped on startup" time="2018-08-13T16:30:09Z" level=info msg="Listening on https://[::]:1338" time="2018-08-13T16:30:09Z" level=info msg="Ansible Service Broker Starting" ERROR: logging before flag.Parse: I0813 16:30:09.600491 1 serve.go:89] Serving securely on [::]:1338 time="2018-08-13T16:30:20Z" level=info msg="AnsibleBroker::Catalog" 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: " 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 time="2018-08-13T16:30:40Z" level=info msg="AnsibleBroker::Catalog" 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: " 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis wrote: > Hello, > > I am seeing the same exact error as Charles under the same conditions -> > installing ASB on Openshift Origin 3.10. > > Regards > > On Thu, Aug 9, 2018 at 8:36 PM David Zager wrote: > >> After reading through the logs and seeing the way the cut off, I'm >> curious if it's related to the `initialDelaySeconds` in the broker's >> deployment config >> . >> With the upstream broker-apb we increased this from 15 seconds to 120 >> . >> I suspect that could be the cause. >> >> >> On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon >> wrote: >> >>> 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. >>> >>> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >>> >>> 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 >>> > >> 1338/ansible-service-broker/v2/catalog>: >>> > dial tcp172.30.206.144:1338 : >>> 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 >> > > wrote: >>> > >>> > Additional info. The ClusterServiceBroker reports this error >>> > >>> > Error fetching catalog. Error getting broker catalog: Get >>> > https://asb.openshift-ansible-service-broker.svc: >>> 1338/ansible-service-broker/v2/catalog >>> > >> 1338/ansible-service-broker/v2/catalog>: >>> > dial tcp 172.30.206.144:1338 : >>> > getsockopt: no route to host >>> > >>> > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard >>> > > 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 : >>> > https://gist.github.com/cmoulliard/ >>> 716468a9e9beb21ba860806a30e3ddcb >>> > >> 716468a9e9beb21ba860806a30e3ddcb> >>> > >>> > 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 >>> > Ansible-service-broker at redhat.com >>> > >>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>> > >>> > >>> > >>> >>> -- >>> Jason Montleon | email: jmontleo at redhat.com >>> Software Engineer | gpg key: 0x069E3022 >>> Red Hat, Inc. | irc: jmontleo >>> desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 >>> <(508)%20496-0663> >>> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dzager at redhat.com Mon Aug 13 16:40:05 2018 From: dzager at redhat.com (David Zager) Date: Mon, 13 Aug 2018 12:40:05 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: An update to the liveness and readiness probes for 3.10 may be appropriate in openshift-ansible. We are intentionally keeping the `dh-automation-broker-apb` out of the list of services. I suspect the issue here is simply with the log level of "not adding spec dh-automation-broker-apb to list of services due to error transforming to service - Could not find the parameter type for: "? On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard wrote: > To get the pod up and running, I have removed the threshold's parameters > from the APB's deployment resource ->liveness and readinessProbes. > > But I see this error now > > time="2018-08-13T16:30:09Z" level=info msg="Broker successfully > bootstrapped on startup" > time="2018-08-13T16:30:09Z" level=info msg="Listening on https:// > [::]:1338" > time="2018-08-13T16:30:09Z" level=info msg="Ansible Service Broker > Starting" > ERROR: logging before flag.Parse: I0813 16:30:09.600491 1 > serve.go:89] Serving securely on [::]:1338 > time="2018-08-13T16:30:20Z" level=info msg="AnsibleBroker::Catalog" > 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: " > 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 > time="2018-08-13T16:30:40Z" level=info msg="AnsibleBroker::Catalog" > 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: " > 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 > > On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis > wrote: > >> Hello, >> >> I am seeing the same exact error as Charles under the same conditions -> >> installing ASB on Openshift Origin 3.10. >> >> Regards >> >> On Thu, Aug 9, 2018 at 8:36 PM David Zager wrote: >> >>> After reading through the logs and seeing the way the cut off, I'm >>> curious if it's related to the `initialDelaySeconds` in the broker's >>> deployment config >>> . >>> With the upstream broker-apb we increased this from 15 seconds to 120 >>> . >>> I suspect that could be the cause. >>> >>> >>> On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon >>> wrote: >>> >>>> 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. >>>> >>>> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >>>> >>>> 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 >>>> >>>> > < >>>> https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog>: >>>> >>>> > dial tcp172.30.206.144:1338 : >>>> 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 < >>>> cmoullia at redhat.com >>>> > > wrote: >>>> > >>>> > Additional info. The ClusterServiceBroker reports this error >>>> > >>>> > Error fetching catalog. Error getting broker catalog: Get >>>> > >>>> https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog >>>> > < >>>> https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog >>>> >: >>>> > dial tcp 172.30.206.144:1338 : >>>> > getsockopt: no route to host >>>> > >>>> > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard >>>> > > 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 : >>>> > >>>> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >>>> > < >>>> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> >>>> > >>>> > 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 >>>> > Ansible-service-broker at redhat.com >>>> > >>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>> > >>>> > >>>> > >>>> >>>> -- >>>> Jason Montleon | email: jmontleo at redhat.com >>>> Software Engineer | gpg key: 0x069E3022 >>>> Red Hat, Inc. | irc: jmontleo >>>> desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 >>>> <(508)%20496-0663> >>>> >>> _______________________________________________ >>> Ansible-service-broker mailing list >>> Ansible-service-broker at redhat.com >>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Aug 13 16:42:28 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 13 Aug 2018 18:42:28 +0200 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: FYI, events still report that the pod is unhealthy 6:39:49 PM Warning Unhealthy Readiness probe failed: Get https://10.128.0.16:1338/healthz: dial tcp 10.128.0.16:1338: getsockopt: connection refused 4 times in the last minute 6:39:45 PM Warning Unhealthy Liveness probe failed: Get https://10.128.0.16:1338/healthz: dial tcp 10.128.0.16:1338: getsockopt: connection refused 2 times in the last and of course, when I browse the catalog, I don't see APB playbooks :-( On Mon, Aug 13, 2018 at 6:40 PM, David Zager wrote: > An update to the liveness and readiness probes for 3.10 may be appropriate > in openshift-ansible. > > We are intentionally keeping the `dh-automation-broker-apb` out of the > list of services. I suspect the issue here is simply with the log level of "not > adding spec dh-automation-broker-apb to list of services due to error > transforming to service - Could not find the parameter type for: "? > > On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard > wrote: > >> To get the pod up and running, I have removed the threshold's parameters >> from the APB's deployment resource ->liveness and readinessProbes. >> >> But I see this error now >> >> time="2018-08-13T16:30:09Z" level=info msg="Broker successfully >> bootstrapped on startup" >> time="2018-08-13T16:30:09Z" level=info msg="Listening on https:// >> [::]:1338" >> time="2018-08-13T16:30:09Z" level=info msg="Ansible Service Broker >> Starting" >> ERROR: logging before flag.Parse: I0813 16:30:09.600491 1 >> serve.go:89] Serving securely on [::]:1338 >> time="2018-08-13T16:30:20Z" level=info msg="AnsibleBroker::Catalog" >> 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: " >> 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET >> /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >> time="2018-08-13T16:30:40Z" level=info msg="AnsibleBroker::Catalog" >> 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: " >> 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET >> /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >> >> On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis < >> gandrian at redhat.com> wrote: >> >>> Hello, >>> >>> I am seeing the same exact error as Charles under the same conditions -> >>> installing ASB on Openshift Origin 3.10. >>> >>> Regards >>> >>> On Thu, Aug 9, 2018 at 8:36 PM David Zager wrote: >>> >>>> After reading through the logs and seeing the way the cut off, I'm >>>> curious if it's related to the `initialDelaySeconds` in the broker's >>>> deployment config >>>> . >>>> With the upstream broker-apb we increased this from 15 seconds to 120 >>>> . >>>> I suspect that could be the cause. >>>> >>>> >>>> On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon >>>> wrote: >>>> >>>>> 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. >>>>> >>>>> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >>>>> >>>>> 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 >>>>> > >>>> 1338/ansible-service-broker/v2/catalog>: >>>>> > dial tcp172.30.206.144:1338 : >>>>> 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 < >>>>> cmoullia at redhat.com >>>>> > > wrote: >>>>> > >>>>> > Additional info. The ClusterServiceBroker reports this error >>>>> > >>>>> > Error fetching catalog. Error getting broker catalog: Get >>>>> > https://asb.openshift-ansible-service-broker.svc: >>>>> 1338/ansible-service-broker/v2/catalog >>>>> > >>>> 1338/ansible-service-broker/v2/catalog>: >>>>> > dial tcp 172.30.206.144:1338 : >>>>> > getsockopt: no route to host >>>>> > >>>>> > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard >>>>> > > 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 : >>>>> > https://gist.github.com/cmoulliard/ >>>>> 716468a9e9beb21ba860806a30e3ddcb >>>>> > >>>> 716468a9e9beb21ba860806a30e3ddcb> >>>>> > >>>>> > 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 >>>>> > Ansible-service-broker at redhat.com >>>>> > >>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>> > >>>>> > >>>>> > >>>>> >>>>> -- >>>>> Jason Montleon | email: jmontleo at redhat.com >>>>> Software Engineer | gpg key: 0x069E3022 >>>>> Red Hat, Inc. | irc: jmontleo >>>>> desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 >>>>> <(508)%20496-0663> >>>>> >>>> _______________________________________________ >>>> Ansible-service-broker mailing list >>>> Ansible-service-broker at redhat.com >>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>> >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Aug 13 16:52:08 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 13 Aug 2018 18:52:08 +0200 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: Is there a reason why we don't install the APB docker image tagged for openshift 3.10 but instead latest ? https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard wrote: > FYI, events still report that the pod is unhealthy > > 6:39:49 PM Warning Unhealthy Readiness probe failed: Get > https://10.128.0.16:1338/healthz: dial tcp 10.128.0.16:1338: getsockopt: > connection refused > 4 times in the last minute > 6:39:45 PM Warning Unhealthy Liveness probe failed: Get > https://10.128.0.16:1338/healthz: dial tcp 10.128.0.16:1338: getsockopt: > connection refused > 2 times in the last > > and of course, when I browse the catalog, I don't see APB playbooks :-( > > > On Mon, Aug 13, 2018 at 6:40 PM, David Zager wrote: > >> An update to the liveness and readiness probes for 3.10 may be >> appropriate in openshift-ansible. >> >> We are intentionally keeping the `dh-automation-broker-apb` out of the >> list of services. I suspect the issue here is simply with the log level of "not >> adding spec dh-automation-broker-apb to list of services due to error >> transforming to service - Could not find the parameter type for: "? >> >> On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard >> wrote: >> >>> To get the pod up and running, I have removed the threshold's parameters >>> from the APB's deployment resource ->liveness and readinessProbes. >>> >>> But I see this error now >>> >>> time="2018-08-13T16:30:09Z" level=info msg="Broker successfully >>> bootstrapped on startup" >>> time="2018-08-13T16:30:09Z" level=info msg="Listening on https:// >>> [::]:1338" >>> time="2018-08-13T16:30:09Z" level=info msg="Ansible Service Broker >>> Starting" >>> ERROR: logging before flag.Parse: I0813 16:30:09.600491 1 >>> serve.go:89] Serving securely on [::]:1338 >>> time="2018-08-13T16:30:20Z" level=info msg="AnsibleBroker::Catalog" >>> 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: " >>> 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET >>> /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >>> time="2018-08-13T16:30:40Z" level=info msg="AnsibleBroker::Catalog" >>> 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: " >>> 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET >>> /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >>> >>> On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis < >>> gandrian at redhat.com> wrote: >>> >>>> Hello, >>>> >>>> I am seeing the same exact error as Charles under the same conditions >>>> -> installing ASB on Openshift Origin 3.10. >>>> >>>> Regards >>>> >>>> On Thu, Aug 9, 2018 at 8:36 PM David Zager wrote: >>>> >>>>> After reading through the logs and seeing the way the cut off, I'm >>>>> curious if it's related to the `initialDelaySeconds` in the broker's >>>>> deployment config >>>>> . >>>>> With the upstream broker-apb we increased this from 15 seconds to 120 >>>>> . >>>>> I suspect that could be the cause. >>>>> >>>>> >>>>> On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon >>>>> wrote: >>>>> >>>>>> 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. >>>>>> >>>>>> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >>>>>> >>>>>> 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 >>>>>> > >>>>> ansible-service-broker/v2/catalog>: >>>>>> > dial tcp172.30.206.144:1338 : >>>>>> 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 < >>>>>> cmoullia at redhat.com >>>>>> > > wrote: >>>>>> > >>>>>> > Additional info. The ClusterServiceBroker reports this error >>>>>> > >>>>>> > Error fetching catalog. Error getting broker catalog: Get >>>>>> > https://asb.openshift-ansible-service-broker.svc:1338/ >>>>>> ansible-service-broker/v2/catalog >>>>>> > >>>>> ansible-service-broker/v2/catalog>: >>>>>> > dial tcp 172.30.206.144:1338 : >>>>>> > getsockopt: no route to host >>>>>> > >>>>>> > On Thu, Aug 9, 2018 at 10:22 AM, Charles Moulliard >>>>>> > > wrote: >>>>>> > >>>>>> > Hi >>>>>> > >>>>>> > I can't install ASB on origin 3.10 anymore using the >>>>>> playbook >>>>>> > "openshift-ansible/playbooks/openshift-service-catalog/conf >>>>>> ig.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 : >>>>>> > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a >>>>>> 30e3ddcb >>>>>> > >>>>> a30e3ddcb> >>>>>> > >>>>>> > 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 >>>>>> > Ansible-service-broker at redhat.com >>>>>> > >>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>> > >>>>> > >>>>>> > >>>>>> > >>>>>> >>>>>> -- >>>>>> Jason Montleon | email: jmontleo at redhat.com >>>>>> Software Engineer | gpg key: 0x069E3022 >>>>>> Red Hat, Inc. | irc: jmontleo >>>>>> desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 >>>>>> <(508)%20496-0663> >>>>>> >>>>> _______________________________________________ >>>>> Ansible-service-broker mailing list >>>>> Ansible-service-broker at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>> >>>> >>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmontleo at redhat.com Mon Aug 13 17:40:19 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Mon, 13 Aug 2018 13:40:19 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: Message-ID: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> Someone recently filed a bug for the v3.10/latest version mismatch. We have some ideas how to handle it better and are working on implementing it for 3.11 (and possibly 3.10). For now it's pretty easy to modify the dc image to get the release you want. oc patch dc -n openshift-automation-service-broker openshift-automation-service-broker --patch='{"spec":{"template":{"spec":{"containers":[{"name": "penshift-automation-service-broker", "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' release-1.0 corresponds to 3.7 release-1.1 3.9 release-1.2 3.10 latest what will become release-1.3 3.11 I'm not sure anything earlier than release-1.2 will work with the resources created by the APB so I'd stick to release-1.2 and latest if you can for now. On 08/13/2018 12:52 PM, Charles Moulliard wrote: > Is there a reason why we don't install the APB docker image tagged for > openshift 3.10 but instead latest? ? > > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > > > On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard > wrote: > > FYI, events still report that the pod is unhealthy > > 6:39:49 PMWarningUnhealthy Readiness probe failed: Get > https://10.128.0.16:1338/healthz : > dial tcp 10.128.0.16:1338 : getsockopt: > connection refused > 4 times in the last minute > 6:39:45 PMWarningUnhealthy Liveness probe failed: Get > https://10.128.0.16:1338/healthz : > dial tcp 10.128.0.16:1338 : getsockopt: > connection refused > 2 times in the last > > and of course, when I browse the catalog, I don't see APB playbooks :-( > > > On Mon, Aug 13, 2018 at 6:40 PM, David Zager > wrote: > > An update to the liveness and readiness probes for 3.10 may be > appropriate in openshift-ansible. > > We are intentionally keeping the `dh-automation-broker-apb` out > of the list of services. I suspect the issue here is simply with > the log level of "not adding spec dh-automation-broker-apb to > list of services due to error transforming to service - Could > not find the parameter type for:?"? > > On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard > > wrote: > > To get the pod up and running, I have removed the > threshold's parameters from the APB's deployment resource > ->liveness and readinessProbes. > > But I see this error now > > time="2018-08-13T16:30:09Z" level=info msg="Broker > successfully bootstrapped on startup" > time="2018-08-13T16:30:09Z" level=info msg="Listening on > https://[::]:1338" > time="2018-08-13T16:30:09Z" level=info msg="Ansible Service > Broker Starting" > ERROR: logging before flag.Parse: I0813 16:30:09.600491 > ?1 serve.go:89] Serving securely on [::]:1338 > time="2018-08-13T16:30:20Z" level=info > msg="AnsibleBroker::Catalog" > 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: " > 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 > time="2018-08-13T16:30:40Z" level=info > msg="AnsibleBroker::Catalog" > 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: " > 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 > > On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis > > wrote: > > Hello, > > I am seeing the same exact error as Charles under the > same conditions -> installing ASB on Openshift Origin 3.10. > > Regards > > On Thu, Aug 9, 2018 at 8:36 PM David Zager > > wrote: > > After reading through the logs and seeing the way > the cut off, I'm curious if it's related to the > `initialDelaySeconds` in the broker's deployment > config > . > With the upstream broker-apb we increased this from > 15 seconds to 120 > . > I suspect that could be the cause. > > > On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon > > > wrote: > > 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. > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > 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 > > > > >: > > > dial tcp172.30.206.144:1338 > : 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 > > >> wrote: > > > >? ? ?Additional info. The ClusterServiceBroker > reports this error > > > >? ? ?Error fetching catalog. Error getting > broker catalog: Get > > > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > ?>: > >? ? ?dial tcp 172.30.206.144:1338 > > : > >? ? ?getsockopt: no route to host > > > >? ? ?On Thu, Aug 9, 2018 at 10:22 AM, Charles > Moulliard > >? ? ? > >> 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 : > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > > ?> > > > >? ? ? ? ?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 > > Ansible-service-broker at redhat.com > > >? ? ? > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > ?> > > > > > > -- > Jason Montleon? ? ?| email: jmontleo at redhat.com > > Software Engineer? | gpg key: 0x069E3022 > Red Hat, Inc.? ? ? | irc: jmontleo > desk: 978-392-3930 | > cell: 508-496-0663 > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From jmontleo at redhat.com Mon Aug 13 19:59:25 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Mon, 13 Aug 2018 15:59:25 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> References: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> Message-ID: <51bff709-e391-97c9-f35a-5aac6d3802dd@redhat.com> FYI: https://bugzilla.redhat.com/show_bug.cgi?id=1612876#c1 On 08/13/2018 01:40 PM, Jason Montleon wrote: > Someone recently filed a bug for the v3.10/latest version mismatch. We > have some ideas how to handle it better and are working on implementing > it for 3.11 (and possibly 3.10). > > For now it's pretty easy to modify the dc image to get the release you > want. > > oc patch dc -n openshift-automation-service-broker > openshift-automation-service-broker > --patch='{"spec":{"template":{"spec":{"containers":[{"name": > "penshift-automation-service-broker", > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > > release-1.0 corresponds to 3.7 > release-1.1 3.9 > release-1.2 3.10 > latest what will become release-1.3 3.11 > > I'm not sure anything earlier than release-1.2 will work with the > resources created by the APB so I'd stick to release-1.2 and latest if > you can for now. > > On 08/13/2018 12:52 PM, Charles Moulliard wrote: >> Is there a reason why we don't install the APB docker image tagged for >> openshift 3.10 but instead latest? ? >> >> https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 >> >> >> >> >> On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard >> > wrote: >> >> ??? FYI, events still report that the pod is unhealthy >> >> ??? 6:39:49 PMWarningUnhealthy Readiness probe failed: Get >> ??? https://10.128.0.16:1338/healthz : >> ??? dial tcp 10.128.0.16:1338 : getsockopt: >> ??? connection refused >> ??? 4 times in the last minute >> ??? 6:39:45 PMWarningUnhealthy Liveness probe failed: Get >> ??? https://10.128.0.16:1338/healthz : >> ??? dial tcp 10.128.0.16:1338 : getsockopt: >> ??? connection refused >> ??? 2 times in the last >> >> ??? and of course, when I browse the catalog, I don't see APB >> playbooks :-( >> >> >> ??? On Mon, Aug 13, 2018 at 6:40 PM, David Zager > ??? > wrote: >> >> ??????? An update to the liveness and readiness probes for 3.10 may be >> ??????? appropriate in openshift-ansible. >> >> ??????? We are intentionally keeping the `dh-automation-broker-apb` out >> ??????? of the list of services. I suspect the issue here is simply with >> ??????? the log level of "not adding spec dh-automation-broker-apb to >> ??????? list of services due to error transforming to service - Could >> ??????? not find the parameter type for:?"? >> >> ??????? On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard >> ??????? > wrote: >> >> ??????????? To get the pod up and running, I have removed the >> ??????????? threshold's parameters from the APB's deployment resource >> ??????????? ->liveness and readinessProbes. >> >> ??????????? But I see this error now >> >> ??????????? time="2018-08-13T16:30:09Z" level=info msg="Broker >> ??????????? successfully bootstrapped on startup" >> ??????????? time="2018-08-13T16:30:09Z" level=info msg="Listening on >> ??????????? https://[::]:1338" >> ??????????? time="2018-08-13T16:30:09Z" level=info msg="Ansible Service >> ??????????? Broker Starting" >> ??????????? ERROR: logging before flag.Parse: I0813 16:30:09.600491 >> ???????????? ?1 serve.go:89] Serving securely on [::]:1338 >> ??????????? time="2018-08-13T16:30:20Z" level=info >> ??????????? msg="AnsibleBroker::Catalog" >> ??????????? 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: " >> ??????????? 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET >> ??????????? /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >> ??????????? time="2018-08-13T16:30:40Z" level=info >> ??????????? msg="AnsibleBroker::Catalog" >> ??????????? 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: " >> ??????????? 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET >> ??????????? /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >> >> ??????????? On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis >> ??????????? > wrote: >> >> ??????????????? Hello, >> >> ??????????????? I am seeing the same exact error as Charles under the >> ??????????????? same conditions -> installing ASB on Openshift Origin >> 3.10. >> >> ??????????????? Regards >> >> ??????????????? On Thu, Aug 9, 2018 at 8:36 PM David Zager >> ??????????????? > wrote: >> >> ??????????????????? After reading through the logs and seeing the way >> ??????????????????? the cut off, I'm curious if it's related to the >> ??????????????????? `initialDelaySeconds` in the broker's deployment >> ??????????????????? config >> >> . >> >> ??????????????????? With the upstream broker-apb we increased this from >> ??????????????????? 15 seconds to 120 >> >> . >> >> ??????????????????? I suspect that could be the cause. >> >> >> ??????????????????? On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon >> ??????????????????? > >> ??????????????????? wrote: >> >> ??????????????????????? 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. >> >> >> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >> >> >> >> ??????????????????????? 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 >> >> >> ???????????????????????? > >> >> > >> >> >: >> >> >> ???????????????????????? > dial tcp172.30.206.144:1338 >> ??????????????????????? : 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 > ??????????????????????? >> ???????????????????????? > > ??????????????????????? >> wrote: >> ???????????????????????? > >> ???????????????????????? >? ? ?Additional info. The ClusterServiceBroker >> ??????????????????????? reports this error >> ???????????????????????? > >> ???????????????????????? >? ? ?Error fetching catalog. Error getting >> ??????????????????????? broker catalog: Get >> ???????????????????????? > >> >> https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog >> >> >> >> >> ???????????????????????? > >> ?> >: >> >> ???????????????????????? >? ? ?dial tcp 172.30.206.144:1338 >> ??????????????????????? >> ??????????????????????? : >> ???????????????????????? >? ? ?getsockopt: no route to host >> ???????????????????????? > >> ???????????????????????? >? ? ?On Thu, Aug 9, 2018 at 10:22 AM, Charles >> ??????????????????????? Moulliard >> ???????????????????????? >? ? ?> ??????????????????????? >> ??????????????????????? > ??????????????????????? >> 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 : >> ???????????????????????? > >> >> https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb >> >> >> ???????????????????????? > >> ?> > >> ???????????????????????? > >> ???????????????????????? >? ? ? ? ?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 >> ???????????????????????? > Ansible-service-broker at redhat.com >> ??????????????????????? >> ???????????????????????? >? ? ?> ??????????????????????? > >> ???????????????????????? > >> >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> >> >> ???????????????????????? > >> ?> > >> ???????????????????????? > >> ???????????????????????? > >> >> ??????????????????????? -- ??????????????????????? Jason Montleon >> ?| email: jmontleo at redhat.com >> ??????????????????????? >> ??????????????????????? Software Engineer? | gpg key: 0x069E3022 >> ??????????????????????? Red Hat, Inc.? ? ? | irc: jmontleo >> ??????????????????????? desk: 978-392-3930 | >> ??????????????????????? cell: 508-496-0663 >> >> ??????????????????? _______________________________________________ >> ??????????????????? Ansible-service-broker mailing list >> ??????????????????? Ansible-service-broker at redhat.com >> ??????????????????? >> >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> >> >> >> >> >> > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From gandrian at redhat.com Tue Aug 14 07:52:55 2018 From: gandrian at redhat.com (Georgios Andrianakis) Date: Tue, 14 Aug 2018 10:52:55 +0300 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> References: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> Message-ID: Hi On Mon, Aug 13, 2018 at 8:40 PM Jason Montleon wrote: > Someone recently filed a bug for the v3.10/latest version mismatch. We > have some ideas how to handle it better and are working on implementing > it for 3.11 (and possibly 3.10). > > For now it's pretty easy to modify the dc image to get the release you > want. > > oc patch dc -n openshift-automation-service-broker > openshift-automation-service-broker > --patch='{"spec":{"template":{"spec":{"containers":[{"name": > "penshift-automation-service-broker", > > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > I tried applying the patch after my Ansible Service Broker installation was failing in the same exact way that Charles mentions, but the odd thing is that I don't have the *openshift-automation-service-b**roker namespace*. Is that to be expected or perhaps some bug? > > release-1.0 corresponds to 3.7 > release-1.1 3.9 > release-1.2 3.10 > latest what will become release-1.3 3.11 > > I'm not sure anything earlier than release-1.2 will work with the > resources created by the APB so I'd stick to release-1.2 and latest if > you can for now. > > On 08/13/2018 12:52 PM, Charles Moulliard wrote: > > Is there a reason why we don't install the APB docker image tagged for > > openshift 3.10 but instead latest ? > > > > > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > > > > > > > On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard > > wrote: > > > > FYI, events still report that the pod is unhealthy > > > > 6:39:49 PMWarningUnhealthy Readiness probe failed: Get > > https://10.128.0.16:1338/healthz : > > dial tcp 10.128.0.16:1338 : getsockopt: > > connection refused > > 4 times in the last minute > > 6:39:45 PMWarningUnhealthy Liveness probe failed: Get > > https://10.128.0.16:1338/healthz : > > dial tcp 10.128.0.16:1338 : getsockopt: > > connection refused > > 2 times in the last > > > > and of course, when I browse the catalog, I don't see APB playbooks > :-( > > > > > > On Mon, Aug 13, 2018 at 6:40 PM, David Zager > > wrote: > > > > An update to the liveness and readiness probes for 3.10 may be > > appropriate in openshift-ansible. > > > > We are intentionally keeping the `dh-automation-broker-apb` out > > of the list of services. I suspect the issue here is simply with > > the log level of "not adding spec dh-automation-broker-apb to > > list of services due to error transforming to service - Could > > not find the parameter type for: "? > > > > On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard > > > wrote: > > > > To get the pod up and running, I have removed the > > threshold's parameters from the APB's deployment resource > > ->liveness and readinessProbes. > > > > But I see this error now > > > > time="2018-08-13T16:30:09Z" level=info msg="Broker > > successfully bootstrapped on startup" > > time="2018-08-13T16:30:09Z" level=info msg="Listening on > > https://[::]:1338" > > time="2018-08-13T16:30:09Z" level=info msg="Ansible Service > > Broker Starting" > > ERROR: logging before flag.Parse: I0813 16:30:09.600491 > > 1 serve.go:89] Serving securely on [::]:1338 > > time="2018-08-13T16:30:20Z" level=info > > msg="AnsibleBroker::Catalog" > > 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: " > > 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET > > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 > > time="2018-08-13T16:30:40Z" level=info > > msg="AnsibleBroker::Catalog" > > 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: " > > 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET > > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 > > > > On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis > > > wrote: > > > > Hello, > > > > I am seeing the same exact error as Charles under the > > same conditions -> installing ASB on Openshift Origin > 3.10. > > > > Regards > > > > On Thu, Aug 9, 2018 at 8:36 PM David Zager > > > wrote: > > > > After reading through the logs and seeing the way > > the cut off, I'm curious if it's related to the > > `initialDelaySeconds` in the broker's deployment > > config > > < > https://github.com/openshift/openshift-ansible/blob/master/roles/ansible_service_broker/templates/asb_dc.yaml.j2#L59-L72 > >. > > With the upstream broker-apb we increased this from > > 15 seconds to 120 > > < > https://github.com/openshift/ansible-service-broker/blob/master/apb/defaults/main.yml#L17 > >. > > I suspect that could be the cause. > > > > > > On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon > > > > > wrote: > > > > 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. > > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> > > > > 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 > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >>: > > > > > dial tcp172.30.206.144:1338 > > : 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 > > > > > >> wrote: > > > > > > Additional info. The ClusterServiceBroker > > reports this error > > > > > > Error fetching catalog. Error getting > > broker catalog: Get > > > > > > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >>: > > > dial tcp 172.30.206.144:1338 > > > > : > > > getsockopt: no route to host > > > > > > On Thu, Aug 9, 2018 at 10:22 AM, Charles > > Moulliard > > > > > > > >> 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 : > > > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb>> > > > > > > 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 > > > Ansible-service-broker at redhat.com > > > > > > > > > > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > < > https://www.redhat.com/mailman/listinfo/ansible-service-broker> > > > > > < > https://www.redhat.com/mailman/listinfo/ansible-service-broker < > https://www.redhat.com/mailman/listinfo/ansible-service-broker>> > > > > > > > > > > -- > > Jason Montleon | email: jmontleo at redhat.com > > > > Software Engineer | gpg key: 0x069E3022 > > Red Hat, Inc. | irc: jmontleo > > desk: 978-392-3930 | > > cell: 508-496-0663 > > > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > < > https://www.redhat.com/mailman/listinfo/ansible-service-broker> > > > > > > > > > > -- > Jason Montleon | email: jmontleo at redhat.com > Software Engineer | gpg key: 0x069E3022 > Red Hat, Inc. | irc: jmontleo > desk: 978-392-3930 | cell: 508-496-0663 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Tue Aug 14 08:01:35 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 14 Aug 2018 10:01:35 +0200 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> Message-ID: I have modified manually the ASB's DC to change the image from latest to 1.3 and I can see the Playbooks now [1] [1] https://www.dropbox.com/s/uvyjfsg3tx75p0s/Screenshot%202018-08-14%2010.00.36.png?dl=0 On Tue, Aug 14, 2018 at 9:52 AM, Georgios Andrianakis wrote: > Hi > > On Mon, Aug 13, 2018 at 8:40 PM Jason Montleon > wrote: > >> Someone recently filed a bug for the v3.10/latest version mismatch. We >> have some ideas how to handle it better and are working on implementing >> it for 3.11 (and possibly 3.10). >> >> For now it's pretty easy to modify the dc image to get the release you >> want. >> >> oc patch dc -n openshift-automation-service-broker >> openshift-automation-service-broker >> --patch='{"spec":{"template":{"spec":{"containers":[{"name": >> "penshift-automation-service-broker", >> "image":"ansibleplaybookbundle/origin-ansible-service-broker: >> release-1.2"}]}}}}' >> > > I tried applying the patch after my Ansible Service Broker installation > was failing in the same exact way that Charles mentions, but the odd thing > is that I don't have the *openshift-automation-service-b**roker namespace*. > Is that to be expected or perhaps some bug? > >> >> release-1.0 corresponds to 3.7 >> release-1.1 3.9 >> release-1.2 3.10 >> latest what will become release-1.3 3.11 >> >> I'm not sure anything earlier than release-1.2 will work with the >> resources created by the APB so I'd stick to release-1.2 and latest if >> you can for now. >> >> On 08/13/2018 12:52 PM, Charles Moulliard wrote: >> > Is there a reason why we don't install the APB docker image tagged for >> > openshift 3.10 but instead latest ? >> > >> > https://github.com/openshift/openshift-ansible/blob/ >> release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 >> > >> > >> > >> > On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard > > > wrote: >> > >> > FYI, events still report that the pod is unhealthy >> > >> > 6:39:49 PMWarningUnhealthy Readiness probe failed: Get >> > https://10.128.0.16:1338/healthz > >: >> > dial tcp 10.128.0.16:1338 : getsockopt: >> > connection refused >> > 4 times in the last minute >> > 6:39:45 PMWarningUnhealthy Liveness probe failed: Get >> > https://10.128.0.16:1338/healthz > >: >> > dial tcp 10.128.0.16:1338 : getsockopt: >> > connection refused >> > 2 times in the last >> > >> > and of course, when I browse the catalog, I don't see APB playbooks >> :-( >> > >> > >> > On Mon, Aug 13, 2018 at 6:40 PM, David Zager > > > wrote: >> > >> > An update to the liveness and readiness probes for 3.10 may be >> > appropriate in openshift-ansible. >> > >> > We are intentionally keeping the `dh-automation-broker-apb` out >> > of the list of services. I suspect the issue here is simply with >> > the log level of "not adding spec dh-automation-broker-apb to >> > list of services due to error transforming to service - Could >> > not find the parameter type for: "? >> > >> > On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard >> > > wrote: >> > >> > To get the pod up and running, I have removed the >> > threshold's parameters from the APB's deployment resource >> > ->liveness and readinessProbes. >> > >> > But I see this error now >> > >> > time="2018-08-13T16:30:09Z" level=info msg="Broker >> > successfully bootstrapped on startup" >> > time="2018-08-13T16:30:09Z" level=info msg="Listening on >> > https://[::]:1338" >> > time="2018-08-13T16:30:09Z" level=info msg="Ansible Service >> > Broker Starting" >> > ERROR: logging before flag.Parse: I0813 16:30:09.600491 >> > 1 serve.go:89] Serving securely on [::]:1338 >> > time="2018-08-13T16:30:20Z" level=info >> > msg="AnsibleBroker::Catalog" >> > 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: " >> > 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET >> > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >> > time="2018-08-13T16:30:40Z" level=info >> > msg="AnsibleBroker::Catalog" >> > 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: " >> > 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET >> > /ansible-service-broker/v2/catalog HTTP/1.1" 200 273918 >> > >> > On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis >> > > wrote: >> > >> > Hello, >> > >> > I am seeing the same exact error as Charles under the >> > same conditions -> installing ASB on Openshift Origin >> 3.10. >> > >> > Regards >> > >> > On Thu, Aug 9, 2018 at 8:36 PM David Zager >> > > wrote: >> > >> > After reading through the logs and seeing the way >> > the cut off, I'm curious if it's related to the >> > `initialDelaySeconds` in the broker's deployment >> > config >> > > blob/master/roles/ansible_service_broker/templates/asb_dc.yaml.j2#L59-L72 >> >. >> > With the upstream broker-apb we increased this from >> > 15 seconds to 120 >> > > broker/blob/master/apb/defaults/main.yml#L17>. >> > I suspect that could be the cause. >> > >> > >> > On Thu, Aug 9, 2018 at 11:37 AM Jason Montleon >> > > >> > wrote: >> > >> > 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. >> > >> > https://gist.github.com/cmoulliard/ >> 716468a9e9beb21ba860806a30e3ddcb >> > > 716468a9e9beb21ba860806a30e3ddcb> >> > >> > 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 >> > >> > > >> > > ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog >> > > ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog>>: >> > >> > > dial tcp172.30.206.144:1338 >> > : 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 > > >> > > > > >> wrote: >> > > >> > > Additional info. The ClusterServiceBroker >> > reports this error >> > > >> > > Error fetching catalog. Error getting >> > broker catalog: Get >> > > >> > https://asb.openshift- >> ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog >> > > ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog> >> > > >> > > ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog < >> https://asb.openshift-ansible-service-broker.svc: >> 1338/ansible-service-broker/v2/catalog>>: >> > > dial tcp 172.30.206.144:1338 >> > >> > : >> > > getsockopt: no route to host >> > > >> > > On Thu, Aug 9, 2018 at 10:22 AM, Charles >> > Moulliard >> > > > > >> > > > >> 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 : >> > > >> > https://gist.github.com/cmoulliard/ >> 716468a9e9beb21ba860806a30e3ddcb >> > > 716468a9e9beb21ba860806a30e3ddcb> >> > > >> > > 716468a9e9beb21ba860806a30e3ddcb > 716468a9e9beb21ba860806a30e3ddcb>> >> > > >> > > 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 >> > > Ansible-service-broker at redhat.com >> > >> > > > broker at redhat.com >> > > >> > > >> > https://www.redhat.com/ >> mailman/listinfo/ansible-service-broker >> > > mailman/listinfo/ansible-service-broker> >> > > >> > > mailman/listinfo/ansible-service-broker > mailman/listinfo/ansible-service-broker>> >> > > >> > > >> > >> > -- >> > Jason Montleon | email: jmontleo at redhat.com >> > >> > Software Engineer | gpg key: 0x069E3022 >> > Red Hat, Inc. | irc: jmontleo >> > desk: 978-392-3930 | >> > cell: 508-496-0663 >> > >> > _______________________________________________ >> > Ansible-service-broker mailing list >> > Ansible-service-broker at redhat.com >> > >> > https://www.redhat.com/mailman/listinfo/ansible- >> service-broker >> > > service-broker> >> > >> > >> > >> > >> >> -- >> Jason Montleon | email: jmontleo at redhat.com >> Software Engineer | gpg key: 0x069E3022 >> Red Hat, Inc. | irc: jmontleo >> desk: 978-392-3930 | cell: 508-496-0663 >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmontleo at redhat.com Tue Aug 14 12:49:11 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Tue, 14 Aug 2018 08:49:11 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> Message-ID: <4b62c930-05c9-5a5f-fc97-9f7a54087301@redhat.com> Sorry, I misunderstood. It sounds like you are using openshift-ansible for the install? I thought you were using oc cluster up --enable=automation-service-broker. You can use these settings for your host to modify the image used during an openshift-ansible install. ansible_service_broker_image_prefix ansible_service_broker_image_tag You could also modify the patch command to work with your installation post install. Something along the lines of: oc patch dc -n openshift-ansible-service-broker asb --patch='{"spec":{"template":{"spec":{"containers":[{"name": "asb", "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' You might do an 'oc get dc -n openshift-ansible-service-broker' and 'oc edit dc -n openshift-ansible-service-broker' to get the correct dc and container names. I am no 100% certain of these off the top of my head. If the default behavior for openshift-ansible with origin isn't what you'd expect it's probably worth filing a bug so we can try to improve it. On 08/14/2018 04:01 AM, Charles Moulliard wrote: > I have modified manually the ASB's DC to change the image from latest to > 1.3 and I can see the Playbooks now [1] > > [1] > https://www.dropbox.com/s/uvyjfsg3tx75p0s/Screenshot%202018-08-14%2010.00.36.png?dl=0 > > On Tue, Aug 14, 2018 at 9:52 AM, Georgios Andrianakis > > wrote: > > Hi > > On Mon, Aug 13, 2018 at 8:40 PM Jason Montleon > wrote: > > Someone recently filed a bug for the v3.10/latest version > mismatch. We > have some ideas how to handle it better and are working on > implementing > it for 3.11 (and possibly 3.10). > > For now it's pretty easy to modify the dc image to get the > release you want. > > oc patch dc -n openshift-automation-service-broker > openshift-automation-service-broker > --patch='{"spec":{"template":{"spec":{"containers":[{"name": > "penshift-automation-service-broker", > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > > I tried applying the patch after my Ansible Service Broker > installation was failing in the same exact way that Charles > mentions, but the odd thing is that I don't have the > /openshift-automation-service-b//roker namespace/. Is that to be > expected or perhaps some bug? > > > release-1.0 corresponds to 3.7 > release-1.1 3.9 > release-1.2 3.10 > latest what will become release-1.3 3.11 > > I'm not sure anything earlier than release-1.2 will work with the > resources created by the APB so I'd stick to release-1.2 and > latest if > you can for now. > > On 08/13/2018 12:52 PM, Charles Moulliard wrote: > > Is there a reason why we don't install the APB docker image > tagged for > > openshift 3.10 but instead latest? ? > > > > > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > > > > > > > > On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard > > > >> wrote: > > > >? ? ?FYI, events still report that the pod is unhealthy > > > >? ? ?6:39:49 PMWarningUnhealthy Readiness probe failed: Get > > https://10.128.0.16:1338/healthz > > >: > >? ? ?dial tcp 10.128.0.16:1338 > : getsockopt: > >? ? ?connection refused > >? ? ?4 times in the last minute > >? ? ?6:39:45 PMWarningUnhealthy Liveness probe failed: Get > > https://10.128.0.16:1338/healthz > > >: > >? ? ?dial tcp 10.128.0.16:1338 > : getsockopt: > >? ? ?connection refused > >? ? ?2 times in the last > > > >? ? ?and of course, when I browse the catalog, I don't see APB > playbooks :-( > > > > > >? ? ?On Mon, Aug 13, 2018 at 6:40 PM, David Zager > > >? ? ?>> wrote: > > > >? ? ? ? ?An update to the liveness and readiness probes for > 3.10 may be > >? ? ? ? ?appropriate in openshift-ansible. > > > >? ? ? ? ?We are intentionally keeping the > `dh-automation-broker-apb` out > >? ? ? ? ?of the list of services. I suspect the issue here is > simply with > >? ? ? ? ?the log level of "not adding spec > dh-automation-broker-apb to > >? ? ? ? ?list of services due to error transforming to service > - Could > >? ? ? ? ?not find the parameter type for:?"? > > > >? ? ? ? ?On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard > >? ? ? ? ? > >> wrote: > > > >? ? ? ? ? ? ?To get the pod up and running, I have removed the > >? ? ? ? ? ? ?threshold's parameters from the APB's deployment > resource > >? ? ? ? ? ? ?->liveness and readinessProbes. > > > >? ? ? ? ? ? ?But I see this error now > > > >? ? ? ? ? ? ?time="2018-08-13T16:30:09Z" level=info msg="Broker > >? ? ? ? ? ? ?successfully bootstrapped on startup" > >? ? ? ? ? ? ?time="2018-08-13T16:30:09Z" level=info > msg="Listening on > >? ? ? ? ? ? ?https://[::]:1338" > >? ? ? ? ? ? ?time="2018-08-13T16:30:09Z" level=info > msg="Ansible Service > >? ? ? ? ? ? ?Broker Starting" > >? ? ? ? ? ? ?ERROR: logging before flag.Parse: I0813 > 16:30:09.600491 > >? ? ? ? ? ? ? ?1 serve.go:89] Serving securely on [::]:1338 > >? ? ? ? ? ? ?time="2018-08-13T16:30:20Z" level=info > >? ? ? ? ? ? ?msg="AnsibleBroker::Catalog" > >? ? ? ? ? ? ?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: " > >? ? ? ? ? ? ?10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET > >? ? ? ? ? ? ?/ansible-service-broker/v2/catalog HTTP/1.1" 200 > 273918 > >? ? ? ? ? ? ?time="2018-08-13T16:30:40Z" level=info > >? ? ? ? ? ? ?msg="AnsibleBroker::Catalog" > >? ? ? ? ? ? ?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: " > >? ? ? ? ? ? ?10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET > >? ? ? ? ? ? ?/ansible-service-broker/v2/catalog HTTP/1.1" 200 > 273918 > > > >? ? ? ? ? ? ?On Fri, Aug 10, 2018 at 8:31 AM, Georgios Andrianakis > >? ? ? ? ? ? ? > >> wrote: > > > >? ? ? ? ? ? ? ? ?Hello, > > > >? ? ? ? ? ? ? ? ?I am seeing the same exact error as Charles > under the > >? ? ? ? ? ? ? ? ?same conditions -> installing ASB on > Openshift Origin 3.10. > > > >? ? ? ? ? ? ? ? ?Regards > > > >? ? ? ? ? ? ? ? ?On Thu, Aug 9, 2018 at 8:36 PM David Zager > >? ? ? ? ? ? ? ? ? > >> wrote: > > > >? ? ? ? ? ? ? ? ? ? ?After reading through the logs and seeing > the way > >? ? ? ? ? ? ? ? ? ? ?the cut off, I'm curious if it's related > to the > >? ? ? ? ? ? ? ? ? ? ?`initialDelaySeconds` in the broker's > deployment > >? ? ? ? ? ? ? ? ? ? ?config > > > ?>. > >? ? ? ? ? ? ? ? ? ? ?With the upstream broker-apb we increased > this from > >? ? ? ? ? ? ? ? ? ? ?15 seconds to 120 > > > ?>. > >? ? ? ? ? ? ? ? ? ? ?I suspect that could be the cause. > > > > > >? ? ? ? ? ? ? ? ? ? ?On Thu, Aug 9, 2018 at 11:37 AM Jason > Montleon > >? ? ? ? ? ? ? ? ? ? ? >> > >? ? ? ? ? ? ? ? ? ? ?wrote: > > > >? ? ? ? ? ? ? ? ? ? ? ? ?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. > > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > > ?> > > > >? ? ? ? ? ? ? ? ? ? ? ? ?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 > > > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > ? > > > ?>>: > > > >? ? ? ? ? ? ? ? ? ? ? ? ? > dial tcp172.30.206.144:1338 > >? ? ? ? ? ? ? ? ? ? ? ? ?: > 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 > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? >>> wrote: > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?Additional info. The > ClusterServiceBroker > >? ? ? ? ? ? ? ? ? ? ? ? ?reports this error > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?Error fetching catalog. Error > getting > >? ? ? ? ? ? ? ? ? ? ? ? ?broker catalog: Get > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > ?> > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > ? >>: > >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?dial tcp 172.30.206.144:1338 > > >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ? ? ? ? ? ? ? ? ?: > >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?getsockopt: no route to host > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?On Thu, Aug 9, 2018 at 10:22 > AM, Charles > >? ? ? ? ? ? ? ? ? ? ? ? ?Moulliard > >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ? > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ? ? ? ? ? ? ? ? ? >>> 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 : > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > > ?> > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > ? >> > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ? ? ?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 > >? ? ? ? ? ? ? ? ? ? ? ? ? > Ansible-service-broker at redhat.com > > > > ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? > > ? > > > ? >> > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > ?> > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > ? >> > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ? > > > > >? ? ? ? ? ? ? ? ? ? ? ? ?-- > >? ? ? ? ? ? ? ? ? ? ? ? ?Jason Montleon? ? ?| email: > jmontleo at redhat.com > >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? ? ? ? ? ? ? ?Software Engineer? | gpg key: 0x069E3022 > >? ? ? ? ? ? ? ? ? ? ? ? ?Red Hat, Inc.? ? ? | irc: jmontleo > >? ? ? ? ? ? ? ? ? ? ? ? ?desk: 978-392-3930 > | > >? ? ? ? ? ? ? ? ? ? ? ? ?cell: 508-496-0663 > > > > > > ?_______________________________________________ > >? ? ? ? ? ? ? ? ? ? ?Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > >? ? ? ? ? ? ? ? ? ? ? > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > ?> > > > > > > > > > > -- > Jason Montleon? ? ?| email: jmontleo at redhat.com > > Software Engineer? | gpg key: 0x069E3022 > Red Hat, Inc.? ? ? | irc: jmontleo > desk: 978-392-3930 | cell: 508-496-0663 > > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From rhallise at redhat.com Tue Aug 14 13:34:56 2018 From: rhallise at redhat.com (rhallise at redhat.com) Date: Tue, 14 Aug 2018 13:34:56 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Weekly from 9:30am to 10:30am on Tuesday from Tue Jul 31 to Mon Aug 13 (EDT) (ansible-service-broker@redhat.com) Message-ID: <00000000000095978805736546d7@google.com> This event has been changed. Title: Automation Broker IRC meeting https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit#heading=h.12ew608coolu Freenode: #asbroker When: Weekly from 9:30am to 10:30am on Tuesday from Tue Jul 31 to Mon Aug 13 Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=NnQ0NjkwdmI4djlxazcxbGs3cGVhM2psMGFfUjIwMTgwNzMxVDEzMzAwMCBhbnNpYmxlLXNlcnZpY2UtYnJva2VyQHJlZGhhdC5jb20&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbWRhNjY3MDU2OGUyYjBkOTUzOTJlMzA3ZTlmYjJmM2Y0MmEwNDIyYzc&ctz=America%2FNew_York&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2098 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2154 bytes Desc: not available URL: From rhallise at redhat.com Tue Aug 14 13:34:56 2018 From: rhallise at redhat.com (rhallise at redhat.com) Date: Tue, 14 Aug 2018 13:34:56 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Weekly from 9:30am to 10:30am on Tuesday from Tue Mar 6 to Mon Aug 13 (EST) (ansible-service-broker@redhat.com) Message-ID: <0000000000009639f705736546dc@google.com> This event has been changed. Title: Automation Broker IRC meeting https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit#heading=h.12ew608coolu Freenode: #asbroker When: Weekly from 9:30am to 10:30am on Tuesday from Tue Mar 6 to Mon Aug 13 Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=NnQ0NjkwdmI4djlxazcxbGs3cGVhM2psMGEgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbWM5ZmIzNTRjYmQ0NWQ5NzJjMjU2MDkyODUxYTE5MWYzNzEzM2RjNzA&ctz=America%2FNew_York&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2056 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2111 bytes Desc: not available URL: From rhallise at redhat.com Tue Aug 14 13:34:56 2018 From: rhallise at redhat.com (rhallise at redhat.com) Date: Tue, 14 Aug 2018 13:34:56 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Every 2 weeks from 9:30am to 10:30am on Tuesday (EDT) (ansible-service-broker@redhat.com) Message-ID: <00000000000097169305736546e8@google.com> This event has been changed. Title: Automation Broker IRC meeting https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit#heading=h.12ew608coolu Freenode: #asbroker When: Every 2 weeks from 9:30am to 10:30am on Tuesday Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=Mmt0NjY4czJ2dm85aHJpcHY2Z25udGp2bDggYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbTRjODViMTk1MTVlMmJkNTY4ZWQ4OWVhYWI1MTAzZjBkZWVmZmNhYjE&ctz=America%2FNew_York&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1647 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1684 bytes Desc: not available URL: From gandrian at redhat.com Tue Aug 14 13:37:45 2018 From: gandrian at redhat.com (Georgios Andrianakis) Date: Tue, 14 Aug 2018 16:37:45 +0300 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: <4b62c930-05c9-5a5f-fc97-9f7a54087301@redhat.com> References: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> <4b62c930-05c9-5a5f-fc97-9f7a54087301@redhat.com> Message-ID: No problem :). Indeed the installation was done via openshift-ansible. Should I open a ticket in openshift-ansible? On Tue, Aug 14, 2018 at 3:49 PM Jason Montleon wrote: > Sorry, I misunderstood. It sounds like you are using openshift-ansible > for the install? I thought you were using oc cluster up > --enable=automation-service-broker. > > You can use these settings for your host to modify the image used during > an openshift-ansible install. > ansible_service_broker_image_prefix > ansible_service_broker_image_tag > > You could also modify the patch command to work with your installation > post install. Something along the lines of: > oc patch dc -n openshift-ansible-service-broker asb > --patch='{"spec":{"template":{"spec":{"containers":[{"name": "asb", > > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > You might do an 'oc get dc -n openshift-ansible-service-broker' and 'oc > edit dc -n openshift-ansible-service-broker' to get the correct dc and > container names. I am no 100% certain of these off the top of my head. > > If the default behavior for openshift-ansible with origin isn't what > you'd expect it's probably worth filing a bug so we can try to improve it. > > > On 08/14/2018 04:01 AM, Charles Moulliard wrote: > > I have modified manually the ASB's DC to change the image from latest to > > 1.3 and I can see the Playbooks now [1] > > > > [1] > > > https://www.dropbox.com/s/uvyjfsg3tx75p0s/Screenshot%202018-08-14%2010.00.36.png?dl=0 > > > > On Tue, Aug 14, 2018 at 9:52 AM, Georgios Andrianakis > > > wrote: > > > > Hi > > > > On Mon, Aug 13, 2018 at 8:40 PM Jason Montleon > > wrote: > > > > Someone recently filed a bug for the v3.10/latest version > > mismatch. We > > have some ideas how to handle it better and are working on > > implementing > > it for 3.11 (and possibly 3.10). > > > > For now it's pretty easy to modify the dc image to get the > > release you want. > > > > oc patch dc -n openshift-automation-service-broker > > openshift-automation-service-broker > > --patch='{"spec":{"template":{"spec":{"containers":[{"name": > > "penshift-automation-service-broker", > > > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > > > > > I tried applying the patch after my Ansible Service Broker > > installation was failing in the same exact way that Charles > > mentions, but the odd thing is that I don't have the > > /openshift-automation-service-b//roker namespace/. Is that to be > > expected or perhaps some bug? > > > > > > release-1.0 corresponds to 3.7 > > release-1.1 3.9 > > release-1.2 3.10 > > latest what will become release-1.3 3.11 > > > > I'm not sure anything earlier than release-1.2 will work with the > > resources created by the APB so I'd stick to release-1.2 and > > latest if > > you can for now. > > > > On 08/13/2018 12:52 PM, Charles Moulliard wrote: > > > Is there a reason why we don't install the APB docker image > > tagged for > > > openshift 3.10 but instead latest ? > > > > > > > > > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > < > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > > > > > > > > > > > > > On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard > > > > > >> > wrote: > > > > > > FYI, events still report that the pod is unhealthy > > > > > > 6:39:49 PMWarningUnhealthy Readiness probe failed: Get > > > https://10.128.0.16:1338/healthz > > > > > >: > > > dial tcp 10.128.0.16:1338 > > : getsockopt: > > > connection refused > > > 4 times in the last minute > > > 6:39:45 PMWarningUnhealthy Liveness probe failed: Get > > > https://10.128.0.16:1338/healthz > > > > > >: > > > dial tcp 10.128.0.16:1338 > > : getsockopt: > > > connection refused > > > 2 times in the last > > > > > > and of course, when I browse the catalog, I don't see APB > > playbooks :-( > > > > > > > > > On Mon, Aug 13, 2018 at 6:40 PM, David Zager > > > > > >> > wrote: > > > > > > An update to the liveness and readiness probes for > > 3.10 may be > > > appropriate in openshift-ansible. > > > > > > We are intentionally keeping the > > `dh-automation-broker-apb` out > > > of the list of services. I suspect the issue here is > > simply with > > > the log level of "not adding spec > > dh-automation-broker-apb to > > > list of services due to error transforming to service > > - Could > > > not find the parameter type for: "? > > > > > > On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard > > > > > >> > wrote: > > > > > > To get the pod up and running, I have removed the > > > threshold's parameters from the APB's deployment > > resource > > > ->liveness and readinessProbes. > > > > > > But I see this error now > > > > > > time="2018-08-13T16:30:09Z" level=info msg="Broker > > > successfully bootstrapped on startup" > > > time="2018-08-13T16:30:09Z" level=info > > msg="Listening on > > > https://[::]:1338" > > > time="2018-08-13T16:30:09Z" level=info > > msg="Ansible Service > > > Broker Starting" > > > ERROR: logging before flag.Parse: I0813 > > 16:30:09.600491 > > > 1 serve.go:89] Serving securely on [::]:1338 > > > time="2018-08-13T16:30:20Z" level=info > > > msg="AnsibleBroker::Catalog" > > > 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: " > > > 10.128.0.1 - - [13/Aug/2018:16:30:20 +0000] "GET > > > /ansible-service-broker/v2/catalog HTTP/1.1" 200 > > 273918 > > > time="2018-08-13T16:30:40Z" level=info > > > msg="AnsibleBroker::Catalog" > > > 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: " > > > 10.128.0.1 - - [13/Aug/2018:16:30:40 +0000] "GET > > > /ansible-service-broker/v2/catalog HTTP/1.1" 200 > > 273918 > > > > > > On Fri, Aug 10, 2018 at 8:31 AM, Georgios > Andrianakis > > > > > >> > wrote: > > > > > > Hello, > > > > > > I am seeing the same exact error as Charles > > under the > > > same conditions -> installing ASB on > > Openshift Origin 3.10. > > > > > > Regards > > > > > > On Thu, Aug 9, 2018 at 8:36 PM David Zager > > > > > >> wrote: > > > > > > After reading through the logs and seeing > > the way > > > the cut off, I'm curious if it's related > > to the > > > `initialDelaySeconds` in the broker's > > deployment > > > config > > > > > < > https://github.com/openshift/openshift-ansible/blob/master/roles/ansible_service_broker/templates/asb_dc.yaml.j2#L59-L72 > < > https://github.com/openshift/openshift-ansible/blob/master/roles/ansible_service_broker/templates/asb_dc.yaml.j2#L59-L72 > >>. > > > With the upstream broker-apb we increased > > this from > > > 15 seconds to 120 > > > > > < > https://github.com/openshift/ansible-service-broker/blob/master/apb/defaults/main.yml#L17 > < > https://github.com/openshift/ansible-service-broker/blob/master/apb/defaults/main.yml#L17 > >>. > > > I suspect that could be the cause. > > > > > > > > > On Thu, Aug 9, 2018 at 11:37 AM Jason > > Montleon > > > > > >> > > > wrote: > > > > > > 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. > > > > > > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb>> > > > > > > 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 > > > > > > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >>>: > > > > > > > dial tcp172.30.206.144:1338 > > > : > > 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 > > > > > > > > > > > > > > > >>> wrote: > > > > > > > > Additional info. The > > ClusterServiceBroker > > > reports this error > > > > > > > > Error fetching catalog. Error > > getting > > > broker catalog: Get > > > > > > > > > > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >> > > > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog> > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >>>: > > > > dial tcp 172.30.206.144:1338 > > > > > > > > : > > > > getsockopt: no route to host > > > > > > > > On Thu, Aug 9, 2018 at 10:22 > > AM, Charles > > > Moulliard > > > > > > > > > > > > > > > > > > >>> 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 : > > > > > > > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb>> > > > > > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb>>> > > > > > > > > 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 > > > > Ansible-service-broker at redhat.com > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > < > https://www.redhat.com/mailman/listinfo/ansible-service-broker < > https://www.redhat.com/mailman/listinfo/ansible-service-broker>> > > > > > > > > > < > https://www.redhat.com/mailman/listinfo/ansible-service-broker < > https://www.redhat.com/mailman/listinfo/ansible-service-broker> < > https://www.redhat.com/mailman/listinfo/ansible-service-broker < > https://www.redhat.com/mailman/listinfo/ansible-service-broker>>> > > > > > > > > > > > > > > -- > > > Jason Montleon | email: > > jmontleo at redhat.com > > > > > > > > Software Engineer | gpg key: > 0x069E3022 > > > Red Hat, Inc. | irc: jmontleo > > > desk: 978-392-3930 > > | > > > cell: 508-496-0663 > > > > > > > > > > _______________________________________________ > > > Ansible-service-broker mailing list > > > Ansible-service-broker at redhat.com > > > > > > > > > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > < > https://www.redhat.com/mailman/listinfo/ansible-service-broker < > https://www.redhat.com/mailman/listinfo/ansible-service-broker>> > > > > > > > > > > > > > > > > -- > > Jason Montleon | email: jmontleo at redhat.com > > > > Software Engineer | gpg key: 0x069E3022 > > Red Hat, Inc. | irc: jmontleo > > desk: 978-392-3930 | cell: 508-496-0663 > > > > > > -- > Jason Montleon | email: jmontleo at redhat.com > Software Engineer | gpg key: 0x069E3022 > Red Hat, Inc. | irc: jmontleo > desk: 978-392-3930 | cell: 508-496-0663 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmontleo at redhat.com Tue Aug 14 13:44:55 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Tue, 14 Aug 2018 09:44:55 -0400 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> <4b62c930-05c9-5a5f-fc97-9f7a54087301@redhat.com> Message-ID: Yes, if the default behavior doesn't look appropriate to you please file a bug and we can see what we can do about improving it there as well. On 08/14/2018 09:37 AM, Georgios Andrianakis wrote: > No problem :). > Indeed the installation was done via openshift-ansible. > > Should I open a ticket in openshift-ansible? > > On Tue, Aug 14, 2018 at 3:49 PM Jason Montleon > wrote: > > Sorry, I misunderstood. It sounds like you are using openshift-ansible > for the install? I thought you were using oc cluster up > --enable=automation-service-broker. > > You can use these settings for your host to modify the image used > during > an openshift-ansible install. > ansible_service_broker_image_prefix > ansible_service_broker_image_tag > > You could also modify the patch command to work with your installation > post install. Something along the lines of: > oc patch dc -n openshift-ansible-service-broker asb > --patch='{"spec":{"template":{"spec":{"containers":[{"name": "asb", > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > You might do an 'oc get dc -n openshift-ansible-service-broker' and 'oc > edit dc -n openshift-ansible-service-broker' to get the correct dc and > container names. I am no 100% certain of these off the top of my head. > > If the default behavior for openshift-ansible with origin isn't what > you'd expect it's probably worth filing a bug so we can try to > improve it. > > > On 08/14/2018 04:01 AM, Charles Moulliard wrote: > > I have modified manually the ASB's DC to change the image from > latest to > > 1.3 and I can see the Playbooks now [1] > > > > [1] > > > https://www.dropbox.com/s/uvyjfsg3tx75p0s/Screenshot%202018-08-14%2010.00.36.png?dl=0 > > > > On Tue, Aug 14, 2018 at 9:52 AM, Georgios Andrianakis > > > >> wrote: > > > >? ? ?Hi > > > >? ? ?On Mon, Aug 13, 2018 at 8:40 PM Jason Montleon > > >? ? ?>> wrote: > > > >? ? ? ? ?Someone recently filed a bug for the v3.10/latest version > >? ? ? ? ?mismatch. We > >? ? ? ? ?have some ideas how to handle it better and are working on > >? ? ? ? ?implementing > >? ? ? ? ?it for 3.11 (and possibly 3.10). > > > >? ? ? ? ?For now it's pretty easy to modify the dc image to get the > >? ? ? ? ?release you want. > > > >? ? ? ? ?oc patch dc -n openshift-automation-service-broker > >? ? ? ? ?openshift-automation-service-broker > >? ? ? ? ?--patch='{"spec":{"template":{"spec":{"containers":[{"name": > >? ? ? ? ?"penshift-automation-service-broker", > > > ?"image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > > > > >? ? ?I tried applying the patch after my Ansible Service Broker > >? ? ?installation was failing in the same exact way that Charles > >? ? ?mentions, but the odd thing is that I don't have the > >? ? ?/openshift-automation-service-b//roker namespace/. Is that to be > >? ? ?expected or perhaps some bug? > > > > > >? ? ? ? ?release-1.0 corresponds to 3.7 > >? ? ? ? ?release-1.1 3.9 > >? ? ? ? ?release-1.2 3.10 > >? ? ? ? ?latest what will become release-1.3 3.11 > > > >? ? ? ? ?I'm not sure anything earlier than release-1.2 will work > with the > >? ? ? ? ?resources created by the APB so I'd stick to release-1.2 and > >? ? ? ? ?latest if > >? ? ? ? ?you can for now. > > > >? ? ? ? ?On 08/13/2018 12:52 PM, Charles Moulliard wrote: > >? ? ? ? ? > Is there a reason why we don't install the APB docker > image > >? ? ? ? ?tagged for > >? ? ? ? ? > openshift 3.10 but instead latest? ? > >? ? ? ? ? > > >? ? ? ? ? > > > > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > > ? > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? > On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard > >? ? ? ? ? > > > >? ? ? ? ? > >>> wrote: > >? ? ? ? ? > > >? ? ? ? ? >? ? ?FYI, events still report that the pod is unhealthy > >? ? ? ? ? > > >? ? ? ? ? >? ? ?6:39:49 PMWarningUnhealthy Readiness probe failed: Get > >? ? ? ? ? > https://10.128.0.16:1338/healthz > >? ? ? ? ? > >? ? ? ? ? >? ? ? ? ?>: > >? ? ? ? ? >? ? ?dial tcp 10.128.0.16:1338 > > >? ? ? ? ?: getsockopt: > >? ? ? ? ? >? ? ?connection refused > >? ? ? ? ? >? ? ?4 times in the last minute > >? ? ? ? ? >? ? ?6:39:45 PMWarningUnhealthy Liveness probe failed: Get > >? ? ? ? ? > https://10.128.0.16:1338/healthz > >? ? ? ? ? > >? ? ? ? ? >? ? ? ? ?>: > >? ? ? ? ? >? ? ?dial tcp 10.128.0.16:1338 > > >? ? ? ? ?: getsockopt: > >? ? ? ? ? >? ? ?connection refused > >? ? ? ? ? >? ? ?2 times in the last > >? ? ? ? ? > > >? ? ? ? ? >? ? ?and of course, when I browse the catalog, I don't > see APB > >? ? ? ? ?playbooks :-( > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? >? ? ?On Mon, Aug 13, 2018 at 6:40 PM, David Zager > >? ? ? ? ? > > > >? ? ? ? ? >? ? ? >>> wrote: > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ?An update to the liveness and readiness probes for > >? ? ? ? ?3.10 may be > >? ? ? ? ? >? ? ? ? ?appropriate in openshift-ansible. > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ?We are intentionally keeping the > >? ? ? ? ?`dh-automation-broker-apb` out > >? ? ? ? ? >? ? ? ? ?of the list of services. I suspect the issue > here is > >? ? ? ? ?simply with > >? ? ? ? ? >? ? ? ? ?the log level of "not adding spec > >? ? ? ? ?dh-automation-broker-apb to > >? ? ? ? ? >? ? ? ? ?list of services due to error transforming to > service > >? ? ? ? ?- Could > >? ? ? ? ? >? ? ? ? ?not find the parameter type for:?"? > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ?On Mon, Aug 13, 2018 at 12:35 PM Charles Moulliard > >? ? ? ? ? >? ? ? ? ? > > >? ? ? ? ? > >>> wrote: > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ?To get the pod up and running, I have > removed the > >? ? ? ? ? >? ? ? ? ? ? ?threshold's parameters from the APB's > deployment > >? ? ? ? ?resource > >? ? ? ? ? >? ? ? ? ? ? ?->liveness and readinessProbes. > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ?But I see this error now > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ?time="2018-08-13T16:30:09Z" level=info > msg="Broker > >? ? ? ? ? >? ? ? ? ? ? ?successfully bootstrapped on startup" > >? ? ? ? ? >? ? ? ? ? ? ?time="2018-08-13T16:30:09Z" level=info > >? ? ? ? ?msg="Listening on > >? ? ? ? ? >? ? ? ? ? ? ?https://[::]:1338" > >? ? ? ? ? >? ? ? ? ? ? ?time="2018-08-13T16:30:09Z" level=info > >? ? ? ? ?msg="Ansible Service > >? ? ? ? ? >? ? ? ? ? ? ?Broker Starting" > >? ? ? ? ? >? ? ? ? ? ? ?ERROR: logging before flag.Parse: I0813 > >? ? ? ? ?16:30:09.600491 > >? ? ? ? ? >? ? ? ? ? ? ? ?1 serve.go:89] Serving securely on [::]:1338 > >? ? ? ? ? >? ? ? ? ? ? ?time="2018-08-13T16:30:20Z" level=info > >? ? ? ? ? >? ? ? ? ? ? ?msg="AnsibleBroker::Catalog" > >? ? ? ? ? >? ? ? ? ? ? ?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: " > >? ? ? ? ? >? ? ? ? ? ? ?10.128.0.1 - - [13/Aug/2018:16:30:20 > +0000] "GET > >? ? ? ? ? >? ? ? ? ? ? ?/ansible-service-broker/v2/catalog > HTTP/1.1" 200 > >? ? ? ? ?273918 > >? ? ? ? ? >? ? ? ? ? ? ?time="2018-08-13T16:30:40Z" level=info > >? ? ? ? ? >? ? ? ? ? ? ?msg="AnsibleBroker::Catalog" > >? ? ? ? ? >? ? ? ? ? ? ?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: " > >? ? ? ? ? >? ? ? ? ? ? ?10.128.0.1 - - [13/Aug/2018:16:30:40 > +0000] "GET > >? ? ? ? ? >? ? ? ? ? ? ?/ansible-service-broker/v2/catalog > HTTP/1.1" 200 > >? ? ? ? ?273918 > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ?On Fri, Aug 10, 2018 at 8:31 AM, Georgios > Andrianakis > >? ? ? ? ? >? ? ? ? ? ? ? > > >? ? ? ? ? > >>> wrote: > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ?Hello, > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ?I am seeing the same exact error as > Charles > >? ? ? ? ?under the > >? ? ? ? ? >? ? ? ? ? ? ? ? ?same conditions -> installing ASB on > >? ? ? ? ?Openshift Origin 3.10. > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ?Regards > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ?On Thu, Aug 9, 2018 at 8:36 PM David Zager > >? ? ? ? ? >? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > >>> wrote: > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?After reading through the logs and > seeing > >? ? ? ? ?the way > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?the cut off, I'm curious if it's > related > >? ? ? ? ?to the > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?`initialDelaySeconds` in the broker's > >? ? ? ? ?deployment > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?config > >? ? ? ? ? > > > > ?>. > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?With the upstream broker-apb we > increased > >? ? ? ? ?this from > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?15 seconds to 120 > >? ? ? ? ? > > > > ?>. > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?I suspect that could be the cause. > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?On Thu, Aug 9, 2018 at 11:37 AM Jason > >? ? ? ? ?Montleon > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ?> > > >? ? ? ? ?>>> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?wrote: > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?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. > >? ? ? ? ? > > >? ? ? ? ? > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > ? > >? ? ? ? ? > > > > ?> > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?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 > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > > > ? > >? ? ? ? ? > > > > ?>>: > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > dial tcp172.30.206.144:1338 > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?: > >? ? ? ? ?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 > >? ? ? ? ?> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ?>> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ?> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ? >>>> wrote: > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?Additional info. The > >? ? ? ? ?ClusterServiceBroker > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?reports this error > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?Error fetching catalog. > Error > >? ? ? ? ?getting > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?broker catalog: Get > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > > > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > ? > >? ? ? ? ? > > > > ?> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > > > ? >>: > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?dial tcp > 172.30.206.144:1338 > >? ? ? ? ? > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?: > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?getsockopt: no route to > host > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ?On Thu, Aug 9, 2018 at > 10:22 > >? ? ? ? ?AM, Charles > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?Moulliard > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ? > >? ? ? ? ?> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ?>> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ?> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ? >>>> 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 : > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > ? > >? ? ? ? ? > > > > ?> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > > > ? >> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? >? ? ? ? ?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 > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > Ansible-service-broker at redhat.com > > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? ? > >? ? ? ? ? >> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? ? > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? ? > >? ? ? ? ? >>> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > ? > >? ? ? ? ? > > > > ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > > > ? > >> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?-- > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?Jason Montleon? ? ?| email: > > jmontleo at redhat.com > > > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ? > >? ? ? ? ?>> > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?Software Engineer? | gpg key: > 0x069E3022 > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?Red Hat, Inc.? ? ? | irc: jmontleo > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?desk: 978-392-3930 > >? ? ? ? ? | > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ? ? ?cell: 508-496-0663 > >? ? ? ? ? > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? ?_______________________________________________ > >? ? ? ? ? >? ? ? ? ? ? ? ? ? ? ?Ansible-service-broker mailing list > >? ? ? ? ? > Ansible-service-broker at redhat.com > > >? ? ? ? ? > > >? ? ? ? ? > > ? > >? ? ? ? ? >> > >? ? ? ? ? > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > ? > >? ? ? ? ? > > > > ? > > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? > > >? ? ? ? ? > > > > >? ? ? ? ?-- > >? ? ? ? ?Jason Montleon? ? ?| email: jmontleo at redhat.com > > >? ? ? ? ?> > >? ? ? ? ?Software Engineer? | gpg key: 0x069E3022 > >? ? ? ? ?Red Hat, Inc.? ? ? | irc: jmontleo > >? ? ? ? ?desk: 978-392-3930 | cell: 508-496-0663 > > > > > > -- > Jason Montleon? ? ?| email: jmontleo at redhat.com > > Software Engineer? | gpg key: 0x069E3022 > Red Hat, Inc.? ? ? | irc: jmontleo > desk: 978-392-3930 | cell: 508-496-0663 > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From gandrian at redhat.com Tue Aug 14 14:21:19 2018 From: gandrian at redhat.com (Georgios Andrianakis) Date: Tue, 14 Aug 2018 17:21:19 +0300 Subject: [Ansible-service-broker] pod can't start when deployed on origin 3.10 In-Reply-To: References: <70041e4e-841d-bbd2-c756-c7bf99ce093c@redhat.com> <4b62c930-05c9-5a5f-fc97-9f7a54087301@redhat.com> Message-ID: I just created a new ticket: https://github.com/openshift/openshift-ansible/issues/9588 Thanks On Tue, Aug 14, 2018 at 4:44 PM Jason Montleon wrote: > Yes, if the default behavior doesn't look appropriate to you please file > a bug and we can see what we can do about improving it there as well. > > On 08/14/2018 09:37 AM, Georgios Andrianakis wrote: > > No problem :). > > Indeed the installation was done via openshift-ansible. > > > > Should I open a ticket in openshift-ansible? > > > > On Tue, Aug 14, 2018 at 3:49 PM Jason Montleon > > wrote: > > > > Sorry, I misunderstood. It sounds like you are using > openshift-ansible > > for the install? I thought you were using oc cluster up > > --enable=automation-service-broker. > > > > You can use these settings for your host to modify the image used > > during > > an openshift-ansible install. > > ansible_service_broker_image_prefix > > ansible_service_broker_image_tag > > > > You could also modify the patch command to work with your > installation > > post install. Something along the lines of: > > oc patch dc -n openshift-ansible-service-broker asb > > --patch='{"spec":{"template":{"spec":{"containers":[{"name": "asb", > > > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > > > You might do an 'oc get dc -n openshift-ansible-service-broker' and > 'oc > > edit dc -n openshift-ansible-service-broker' to get the correct dc > and > > container names. I am no 100% certain of these off the top of my > head. > > > > If the default behavior for openshift-ansible with origin isn't what > > you'd expect it's probably worth filing a bug so we can try to > > improve it. > > > > > > On 08/14/2018 04:01 AM, Charles Moulliard wrote: > > > I have modified manually the ASB's DC to change the image from > > latest to > > > 1.3 and I can see the Playbooks now [1] > > > > > > [1] > > > > > > https://www.dropbox.com/s/uvyjfsg3tx75p0s/Screenshot%202018-08-14%2010.00.36.png?dl=0 > > > > > > On Tue, Aug 14, 2018 at 9:52 AM, Georgios Andrianakis > > > > > >> wrote: > > > > > > Hi > > > > > > On Mon, Aug 13, 2018 at 8:40 PM Jason Montleon > > > > > >> > wrote: > > > > > > Someone recently filed a bug for the v3.10/latest version > > > mismatch. We > > > have some ideas how to handle it better and are working on > > > implementing > > > it for 3.11 (and possibly 3.10). > > > > > > For now it's pretty easy to modify the dc image to get the > > > release you want. > > > > > > oc patch dc -n openshift-automation-service-broker > > > openshift-automation-service-broker > > > > --patch='{"spec":{"template":{"spec":{"containers":[{"name": > > > "penshift-automation-service-broker", > > > > > > "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}' > > > > > > > > > I tried applying the patch after my Ansible Service Broker > > > installation was failing in the same exact way that Charles > > > mentions, but the odd thing is that I don't have the > > > /openshift-automation-service-b//roker namespace/. Is that to > be > > > expected or perhaps some bug? > > > > > > > > > release-1.0 corresponds to 3.7 > > > release-1.1 3.9 > > > release-1.2 3.10 > > > latest what will become release-1.3 3.11 > > > > > > I'm not sure anything earlier than release-1.2 will work > > with the > > > resources created by the APB so I'd stick to release-1.2 > and > > > latest if > > > you can for now. > > > > > > On 08/13/2018 12:52 PM, Charles Moulliard wrote: > > > > Is there a reason why we don't install the APB docker > > image > > > tagged for > > > > openshift 3.10 but instead latest ? > > > > > > > > > > > > > > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > > > > < > https://github.com/openshift/openshift-ansible/blob/release-3.10/roles/ansible_service_broker/defaults/main.yml#L26 > > > > > > > > > > > > > > > > > > On Mon, Aug 13, 2018 at 6:42 PM, Charles Moulliard > > > > > > > > > > > > >>> wrote: > > > > > > > > FYI, events still report that the pod is unhealthy > > > > > > > > 6:39:49 PMWarningUnhealthy Readiness probe failed: > Get > > > > https://10.128.0.16:1338/healthz > > > > > > > > >: > > > > dial tcp 10.128.0.16:1338 > > > > > : getsockopt: > > > > connection refused > > > > 4 times in the last minute > > > > 6:39:45 PMWarningUnhealthy Liveness probe failed: > Get > > > > https://10.128.0.16:1338/healthz > > > > > > > > >: > > > > dial tcp 10.128.0.16:1338 > > > > > : getsockopt: > > > > connection refused > > > > 2 times in the last > > > > > > > > and of course, when I browse the catalog, I don't > > see APB > > > playbooks :-( > > > > > > > > > > > > On Mon, Aug 13, 2018 at 6:40 PM, David Zager > > > > > > > > > > > > >>> wrote: > > > > > > > > An update to the liveness and readiness probes > for > > > 3.10 may be > > > > appropriate in openshift-ansible. > > > > > > > > We are intentionally keeping the > > > `dh-automation-broker-apb` out > > > > of the list of services. I suspect the issue > > here is > > > simply with > > > > the log level of "not adding spec > > > dh-automation-broker-apb to > > > > list of services due to error transforming to > > service > > > - Could > > > > not find the parameter type for: "? > > > > > > > > On Mon, Aug 13, 2018 at 12:35 PM Charles > Moulliard > > > > > > > > > > > > >>> wrote: > > > > > > > > To get the pod up and running, I have > > removed the > > > > threshold's parameters from the APB's > > deployment > > > resource > > > > ->liveness and readinessProbes. > > > > > > > > But I see this error now > > > > > > > > time="2018-08-13T16:30:09Z" level=info > > msg="Broker > > > > successfully bootstrapped on startup" > > > > time="2018-08-13T16:30:09Z" level=info > > > msg="Listening on > > > > https://[::]:1338" > > > > time="2018-08-13T16:30:09Z" level=info > > > msg="Ansible Service > > > > Broker Starting" > > > > ERROR: logging before flag.Parse: I0813 > > > 16:30:09.600491 > > > > 1 serve.go:89] Serving securely on > [::]:1338 > > > > time="2018-08-13T16:30:20Z" level=info > > > > msg="AnsibleBroker::Catalog" > > > > 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: " > > > > 10.128.0.1 - - [13/Aug/2018:16:30:20 > > +0000] "GET > > > > /ansible-service-broker/v2/catalog > > HTTP/1.1" 200 > > > 273918 > > > > time="2018-08-13T16:30:40Z" level=info > > > > msg="AnsibleBroker::Catalog" > > > > 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: " > > > > 10.128.0.1 - - [13/Aug/2018:16:30:40 > > +0000] "GET > > > > /ansible-service-broker/v2/catalog > > HTTP/1.1" 200 > > > 273918 > > > > > > > > On Fri, Aug 10, 2018 at 8:31 AM, Georgios > > Andrianakis > > > > > > > > > > > > >>> wrote: > > > > > > > > Hello, > > > > > > > > I am seeing the same exact error as > > Charles > > > under the > > > > same conditions -> installing ASB on > > > Openshift Origin 3.10. > > > > > > > > Regards > > > > > > > > On Thu, Aug 9, 2018 at 8:36 PM David > Zager > > > > > > > > > > > > >>> wrote: > > > > > > > > After reading through the logs and > > seeing > > > the way > > > > the cut off, I'm curious if it's > > related > > > to the > > > > `initialDelaySeconds` in the > broker's > > > deployment > > > > config > > > > > > > > > < > https://github.com/openshift/openshift-ansible/blob/master/roles/ansible_service_broker/templates/asb_dc.yaml.j2#L59-L72 > < > https://github.com/openshift/openshift-ansible/blob/master/roles/ansible_service_broker/templates/asb_dc.yaml.j2#L59-L72 > >>. > > > > With the upstream broker-apb we > > increased > > > this from > > > > 15 seconds to 120 > > > > > > > > > < > https://github.com/openshift/ansible-service-broker/blob/master/apb/defaults/main.yml#L17 > < > https://github.com/openshift/ansible-service-broker/blob/master/apb/defaults/main.yml#L17 > >>. > > > > I suspect that could be the cause. > > > > > > > > > > > > On Thu, Aug 9, 2018 at 11:37 AM > Jason > > > Montleon > > > > > > > > > > > > > > >>>> > > > > wrote: > > > > > > > > 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. > > > > > > > > > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> > > > > > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb>> > > > > > > > > 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 > > > > > > > > > > > > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >>>: > > > > > > > > > dial tcp172.30.206.144:1338 > > > > : > > > 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 > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > > > > >>>> wrote: > > > > > > > > > > Additional info. The > > > ClusterServiceBroker > > > > reports this error > > > > > > > > > > Error fetching catalog. > > Error > > > getting > > > > broker catalog: Get > > > > > > > > > > > > > > > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > > > > > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >> > > > > > > > > > > > > > > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog> > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > < > https://asb.openshift-ansible-service-broker.svc:1338/ansible-service-broker/v2/catalog > >>>: > > > > > dial tcp > > 172.30.206.144:1338 > > > > > > > > > > > : > > > > > getsockopt: no route to > > host > > > > > > > > > > On Thu, Aug 9, 2018 at > > 10:22 > > > AM, Charles > > > > Moulliard > > > > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > > > >>>> 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 : > > > > > > > > > > > > > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> > > > > > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb>> > > > > > > > > > > > > > > < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb> < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb < > https://gist.github.com/cmoulliard/716468a9e9beb21ba860806a30e3ddcb>>> > > > > > > > > > > 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 > > > > > > > Ansible-service-broker at redhat.com > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > -- > > > > Jason Montleon | email: > > > jmontleo at redhat.com > > > > > > > > > > > >>> > > > > Software Engineer | gpg key: > > 0x069E3022 > > > > Red Hat, Inc. | irc: > jmontleo > > > > desk: 978-392-3930 > > > | > > > > cell: 508-496-0663 > > > > > > > > > > > > > > _______________________________________________ > > > > Ansible-service-broker mailing list > > > > Ansible-service-broker at redhat.com > > > > > > > > > > > > > > > > > > >> > > > > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Jason Montleon | email: jmontleo at redhat.com > > > > > > > > > Software Engineer | gpg key: 0x069E3022 > > > Red Hat, Inc. | irc: jmontleo > > > desk: 978-392-3930 | cell: 508-496-0663 > > > > > > > > > > -- > > Jason Montleon | email: jmontleo at redhat.com > > > > Software Engineer | gpg key: 0x069E3022 > > Red Hat, Inc. | irc: jmontleo > > desk: 978-392-3930 | cell: 508-496-0663 > > > > -- > Jason Montleon | email: jmontleo at redhat.com > Software Engineer | gpg key: 0x069E3022 > Red Hat, Inc. | irc: jmontleo > desk: 978-392-3930 | cell: 508-496-0663 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesusr at redhat.com Tue Aug 14 15:55:04 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 14 Aug 2018 11:55:04 -0400 Subject: [Ansible-service-broker] bundle-lib release 0.2.8 done Message-ID: <174f95143954c5c9a0c79e4c96dd08ea58dac6b6.camel@redhat.com> Today we release bundle-lib 0.2.8 where we addressed a few bugs. ### Bugs * Bug 1583049 - Add metrics (#161) * Bug 1609700 - Use config user/pass if no auth_type (#160) * Issue 158 - remove useless debug statements (#159) ### Enhancements * Apply consistent labels to credential secrets (#157) * Ensure tag is added to local_openshift specs (#162) https://github.com/automationbroker/bundle-lib/releases/tag/0.2.8 jesus From jesusr at redhat.com Tue Aug 21 14:08:07 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 21 Aug 2018 10:08:07 -0400 Subject: [Ansible-service-broker] Automation Broker IRC meeting 2018-08-21 Message-ID: <6dd2196312dfcb58fed7a8c5ca4b96fe59066cb2.camel@redhat.com> ============================================================ #asbroker: Automation Broker IRC Community Meeting 8/21/2018 ============================================================ Meeting started by jmrodri at 13:30:31 UTC. The full logs are available at asbroker/2018/asbroker.2018-08-21-13.30.log.html . Meeting summary --------------- * Attendance (jmrodri, 13:30:41) * News (jmrodri, 13:32:15) * we released bundle-lib 0.2.9, will probably do another release this week (jmrodri, 13:32:49) * LINK: https://github.com/automationbroker/bundle-lib/releases/tag/0.2.9 (jmrodri, 13:32:58) * automation-broker 1.3.9-1 was released last night. Just checkout that tag if you want to build it from source. Or grab one of the nightly images (jmrodri, 13:33:47) * review previous actions (jmrodri, 13:35:56) * issue 470 was closed as complete. (jmrodri, 13:36:52) * LINK: https://github.com/openshift/ansible-service-broker/issues/470 (jmrodri, 13:36:58) * issue 1028 assigned to jmrodri (jmrodri, 13:37:18) * LINK: https://github.com/openshift/ansible-service-broker/issues/1028 (jmrodri, 13:37:28) * issue 974 reassigned to jmrodri (jmrodri, 13:37:52) * switch irc meeting to bi-weekly. (jmrodri, 13:38:13) * Failed provision triggers continuous deprovision (jmrodri, 13:39:07) * LINK: https://github.com/openshift/ansible-service-broker/issues/1010 (jmrodri, 13:39:09) * LINK: https://github.com/openshift/ansible-service-broker/blob/master/docs/meetings/2018/asbroker.2018-08-07-13.32.log.txt#L75-L114 (jmrodri, 13:40:05) * ACTION: jmrodri create issue for rate limiter feature (jmrodri, 13:41:19) * bugs/issue triage (jmrodri, 13:41:40) * bundle-lib has 9 issues still, hasn't changed since the last meeting (jmrodri, 13:42:06) * LINK: https://github.com/automationbroker/bundle-lib/issues (jmrodri, 13:42:29) * automation broker issues (jmrodri, 13:44:59) * LINK: https://github.com/openshift/ansible-service-broker/issues?q=is%3Aissue+is%3Aopen+label%3A%223.11+%7C+release-1.3%22 (jmrodri, 13:45:21) * LINK: https://github.com/openshift/ansible-service-broker/issues?q=is%3Aissue+is%3Aopen+label%3A%223.11+%7C+release-1.3%22 (jmrodri, 13:45:31) * ACTION: jmrodri test the 2 async bind issues in automation-broker: 1007 and 1006 (jmrodri, 13:46:20) * Importing APBs fail if an image repo in the dockerhub org doesn't have any tags (jmrodri, 13:46:53) * LINK: https://github.com/openshift/ansible-service-broker/issues/1037 (jmrodri, 13:47:00) * ACTION: dymurrayRH to investigate broker issue 1037 (jmrodri, 13:54:58) * features (jmrodri, 13:55:37) * none at this moment (jmrodri, 13:55:46) * open discussion (jmrodri, 13:55:55) * postgresql-apb latest (jmrodri, 13:56:14) * ACTION: dzager investigate how best to repair psql -apb latest image without rebuilding the world (jmrodri, 13:59:25) Meeting ended at 14:02:28 UTC. Action Items ------------ * jmrodri create issue for rate limiter feature * jmrodri test the 2 async bind issues in automation-broker: 1007 and 1006 * dymurrayRH to investigate broker issue 1037 * dzager investigate how best to repair psql -apb latest image without rebuilding the world Action Items, by person ----------------------- * dymurrayRH * dymurrayRH to investigate broker issue 1037 * dzager * dzager investigate how best to repair psql -apb latest image without rebuilding the world * jmrodri * jmrodri create issue for rate limiter feature * jmrodri test the 2 async bind issues in automation-broker: 1007 and 1006 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jmrodri (78) * brokerbot (33) * dzager (12) * ernelson (4) * dymurrayRH (3) * alpatel (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From cmoullia at redhat.com Mon Aug 27 16:33:42 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 27 Aug 2018 18:33:42 +0200 Subject: [Ansible-service-broker] Question about a misterious secret created Message-ID: Hi, I'm using golang kubernetes service catalog API to create a service instance using openshift automation service broker Code to create the service [1] To do the binding [2] The service instance is well created but when I do the binding I get an error reporing that secret already exists svcat describe bindings my-postgresql-db Name: my-postgresql-db Namespace: crud Status: Failed - ServiceBroker returned failure; bind operation will not be retried: Status: 400; ErrorMessage: ; Description: secrets "a7c00676-4398-11e8-842f-0ed5f89f718b" already exists; ResponseError: @ 2018-08-27 16:27:28 +0000 UTC Secret: my-postgresql-db-credentials Instance: my-postgresql-db Question: What should I do to resolve the issue ? [1] https://goo.gl/36n2U4 [2] https://goo.gl/CzTpjP Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Aug 27 18:31:37 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 27 Aug 2018 20:31:37 +0200 Subject: [Ansible-service-broker] Question about a misterious secret created In-Reply-To: References: Message-ID: - You can reproduce the error if you git clone my project within your $GOPATH folder git clone https://github.com/snowdrop/k8s-supervisor.git or go get ... - Next run this command with openshift 3.10 + ASB broker running and namespace `crud` created go run *.go catalog create Remark : minishift has been started as such -> https://goo.gl/b3mcZQ On Mon, Aug 27, 2018 at 6:33 PM, Charles Moulliard wrote: > Hi, > > I'm using golang kubernetes service catalog API to create a service > instance using openshift automation service broker > > Code to create the service [1] > To do the binding [2] > > The service instance is well created but when I do the binding I get an > error reporing that secret already exists > > svcat describe bindings my-postgresql-db > > Name: my-postgresql-db > > > > Namespace: crud > > > > Status: Failed - ServiceBroker returned failure; bind operation > will not be retried: Status: 400; ErrorMessage: ; Description: secrets > "a7c00676-4398-11e8-842f-0ed5f89f718b" already exists; ResponseError: > @ 2018-08-27 16:27:28 +0000 UTC > Secret: my-postgresql-db-credentials > > > > Instance: my-postgresql-db > > > > > Question: What should I do to resolve the issue ? > > [1] https://goo.gl/36n2U4 > [2] https://goo.gl/CzTpjP > > Regards > > Charles > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesusr at redhat.com Mon Aug 27 20:39:10 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Mon, 27 Aug 2018 16:39:10 -0400 Subject: [Ansible-service-broker] Question about a misterious secret created In-Reply-To: References: Message-ID: Charles, I haven't found the fix yet, but I did see a pattern. I was able to recreate the problem using the commands you defined below, as well as with a script I have to create binds. The pattern is that the very first bind request returns an error *IF* the bind id is the same as the instance id because of the secret created during the provision call. Subsequent calls seem to work even if they have the same id. I'm still trying to track down why that first one is failing while the others work fine. One short term solution is to use a different uuid for the binding that is not the same as the instance id. https://github.com/snowdrop/k8s-supervisor/blob/master/pkg/catalog/bind.go#L37 Sincerely, jesus On Mon, 2018-08-27 at 20:31 +0200, Charles Moulliard wrote: > - You can reproduce the error if you git clone my project within your > $GOPATH folder > git clone https://github.com/snowdrop/k8s-supervisor.git or go get > ... > - Next run this command with openshift 3.10 + ASB broker running and > namespace `crud` created > go run *.go catalog create > > Remark : minishift has been started as such -> https://goo.gl/b3mcZQ > > On Mon, Aug 27, 2018 at 6:33 PM, Charles Moulliard < > cmoullia at redhat.com> > wrote: > > > Hi, > > > > I'm using golang kubernetes service catalog API to create a service > > instance using openshift automation service broker > > > > Code to create the service [1] > > To do the binding [2] > > > > The service instance is well created but when I do the binding I > > get an > > error reporing that secret already exists > > > > svcat describe bindings my-postgresql-db > > > > Name: my-postgresql-db > > > > > > > > Namespace: crud > > > > > > > > Status: Failed - ServiceBroker returned failure; bind > > operation > > will not be retried: Status: 400; ErrorMessage: ; Description: > > secrets > > "a7c00676-4398-11e8-842f-0ed5f89f718b" already exists; > > ResponseError: > > @ 2018-08-27 16:27:28 +0000 UTC > > Secret: my-postgresql-db-credentials > > > > > > > > Instance: my-postgresql-db > > > > > > > > > > Question: What should I do to resolve the issue ? > > > > [1] https://goo.gl/36n2U4 > > [2] https://goo.gl/CzTpjP > > > > Regards > > > > Charles > > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker From cmoullia at redhat.com Tue Aug 28 04:59:44 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 28 Aug 2018 06:59:44 +0200 Subject: [Ansible-service-broker] Question about a misterious secret created In-Reply-To: References: Message-ID: Many thanks for your help and the trick. I have changed the code to generate a UUID and that works // Generate UUID ottherwise binding will fail if we use same id as the instanceName, bidingName UUID := string(uuid.NewUUID()) log.Infof("Let's generate a secret containing the parameters to be used by the application") bind(serviceCatalogClient,NS,INSTANCE_NAME,EXTERNAL_ID, INSTANCE_NAME,UUID,nil,nil) Additional question Do you know which API should I use to mount the secret of the binding into a deploymentConfig/Pod - similar to what the OpenShift UI offers [1] ? [1] https://www.dropbox.com/s/45rbk9htvaiqrt4/Screenshot%202018-08-28%2006.57.34.png?dl=0 On Mon, Aug 27, 2018 at 10:39 PM, wrote: > Charles, > > I haven't found the fix yet, but I did see a pattern. I was able to > recreate the problem using the commands you defined below, as well as > with a script I have to create binds. > > The pattern is that the very first bind request returns an error *IF* > the bind id is the same as the instance id because of the secret > created during the provision call. Subsequent calls seem to work even > if they have the same id. > > I'm still trying to track down why that first one is failing while the > others work fine. > > One short term solution is to use a different uuid for the binding that > is not the same as the instance id. > > > https://github.com/snowdrop/k8s-supervisor/blob/master/pkg/ > catalog/bind.go#L37 > > Sincerely, > jesus > > On Mon, 2018-08-27 at 20:31 +0200, Charles Moulliard wrote: > > - You can reproduce the error if you git clone my project within your > > $GOPATH folder > > git clone https://github.com/snowdrop/k8s-supervisor.git or go get > > ... > > - Next run this command with openshift 3.10 + ASB broker running and > > namespace `crud` created > > go run *.go catalog create > > > > Remark : minishift has been started as such -> https://goo.gl/b3mcZQ > > > > On Mon, Aug 27, 2018 at 6:33 PM, Charles Moulliard < > > cmoullia at redhat.com> > > wrote: > > > > > Hi, > > > > > > I'm using golang kubernetes service catalog API to create a service > > > instance using openshift automation service broker > > > > > > Code to create the service [1] > > > To do the binding [2] > > > > > > The service instance is well created but when I do the binding I > > > get an > > > error reporing that secret already exists > > > > > > svcat describe bindings my-postgresql-db > > > > > > Name: my-postgresql-db > > > > > > > > > > > > Namespace: crud > > > > > > > > > > > > Status: Failed - ServiceBroker returned failure; bind > > > operation > > > will not be retried: Status: 400; ErrorMessage: ; Description: > > > secrets > > > "a7c00676-4398-11e8-842f-0ed5f89f718b" already exists; > > > ResponseError: > > > @ 2018-08-27 16:27:28 +0000 UTC > > > Secret: my-postgresql-db-credentials > > > > > > > > > > > > Instance: my-postgresql-db > > > > > > > > > > > > > > > Question: What should I do to resolve the issue ? > > > > > > [1] https://goo.gl/36n2U4 > > > [2] https://goo.gl/CzTpjP > > > > > > Regards > > > > > > Charles > > > > > > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Thu Aug 30 08:02:52 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 30 Aug 2018 10:02:52 +0200 Subject: [Ansible-service-broker] Make a service available even if we see -> out of bounds 1.0 <= 1.0 Message-ID: Hi Is it possible to also use a service/class even if we see such warning message inot the log of hr ASB's pod "[2018-08-30T07:52:21.984Z] [WARNING] - Spec [ postgresql-apb ] failed validation for the following reason: [ APB Spec version [1.0.0] out of bounds 1.0 <= 1.0 ]. It will not be made available." ? What is the trick to allow to by pass such restriction ? Regards charles -------------- next part -------------- An HTML attachment was scrubbed... URL: