From cmoullia at redhat.com Wed Nov 7 21:19:07 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Wed, 7 Nov 2018 22:19:07 +0100 Subject: [Ansible-service-broker] Can OAB be deployed on k8s ? Message-ID: Hi I'm trying to install OAB on k8s v1.11 according to the info reported here [1] and that fails as the k8s service catalog can't access the broker [2] Can OAB be deployed on k8s ? Is there a workaround ? [1] https://blog.openshift.com/automation-broker-discovering-helm-charts/ [2] https://goo.gl/8F3WxV Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Thu Nov 8 06:04:11 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 8 Nov 2018 07:04:11 +0100 Subject: [Ansible-service-broker] Can OAB be deployed on k8s ? In-Reply-To: References: Message-ID: When the pod of OAB starts, then this error message appears [2018-11-08T05:18:28.93Z] [DEBUG] - Creating k8s apiserver [2018-11-08T05:18:28.932Z] [ERROR] - Unable to retrieve cluster roles rules from cluster You must be using OpenShift 3.7 to use the User rules check. clusterroles.rbac.authorization.k8s.io "admin" is forbidden: User "system:serviceaccount:automation-broker:automation-broker" cannot get clusterroles.rbac.authorization.k8s.io at the cluster scope On Wed, Nov 7, 2018 at 10:19 PM Charles Moulliard wrote: > Hi > > I'm trying to install OAB on k8s v1.11 according to the info reported here > [1] and that fails as the k8s service catalog can't access the broker [2] > > Can OAB be deployed on k8s ? Is there a workaround ? > > [1] https://blog.openshift.com/automation-broker-discovering-helm-charts/ > [2] https://goo.gl/8F3WxV > > Regards > > Charles > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shurley at redhat.com Thu Nov 8 15:30:32 2018 From: shurley at redhat.com (Shawn Hurley) Date: Thu, 8 Nov 2018 10:30:32 -0500 Subject: [Ansible-service-broker] Can OAB be deployed on k8s ? In-Reply-To: References: Message-ID: Which version of the automation broker are you using and how are you deploying? I think you will probably want to look into either the 1. Auto Escalate config value or 2. The permissions of the automation-broker that you are granting Thanks, Shawn Hurley On Thu, Nov 8, 2018 at 1:10 AM Charles Moulliard wrote: > > When the pod of OAB starts, then this error message appears > > [2018-11-08T05:18:28.93Z] [DEBUG] - Creating k8s apiserver > [2018-11-08T05:18:28.932Z] [ERROR] - Unable to retrieve cluster roles rules from cluster > You must be using OpenShift 3.7 to use the User rules check. > clusterroles.rbac.authorization.k8s.io "admin" is forbidden: User "system:serviceaccount:automation-broker:automation-broker" cannot get clusterroles.rbac.authorization.k8s.io at the cluster scope > > > > > On Wed, Nov 7, 2018 at 10:19 PM Charles Moulliard wrote: >> >> Hi >> >> I'm trying to install OAB on k8s v1.11 according to the info reported here [1] and that fails as the k8s service catalog can't access the broker [2] >> >> Can OAB be deployed on k8s ? Is there a workaround ? >> >> [1] https://blog.openshift.com/automation-broker-discovering-helm-charts/ >> [2] https://goo.gl/8F3WxV >> >> 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 Thu Nov 8 16:10:09 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 8 Nov 2018 17:10:09 +0100 Subject: [Ansible-service-broker] Can OAB be deployed on k8s ? In-Reply-To: References: Message-ID: Hi Shawn I was able to install OAB using the following instructions [1] [2]. [1] K8s Service Catalog : https://github.com/cmoulliard/cloud-native/blob/master/play-with-k8s-catalog.md#get-and-install-helm-chart-of-the-service-catalog [2] OAB : https://github.com/cmoulliard/cloud-native/blob/master/play-with-k8s-catalog.md#install-oab Nevertheless, some of the plans were not created or visible when I was issuing the command `svcat get plans` and by consequence it has been impossible to create a serviceInstance Regards Charles On Thu, Nov 8, 2018 at 4:30 PM Shawn Hurley wrote: > Which version of the automation broker are you using and how are you > deploying? I think you will probably want to look into either the 1. > Auto Escalate config value or 2. The permissions of the > automation-broker that you are granting > > Thanks, > > Shawn Hurley > On Thu, Nov 8, 2018 at 1:10 AM Charles Moulliard > wrote: > > > > When the pod of OAB starts, then this error message appears > > > > [2018-11-08T05:18:28.93Z] [DEBUG] - Creating k8s apiserver > > [2018-11-08T05:18:28.932Z] [ERROR] - Unable to retrieve cluster roles > rules from cluster > > You must be using OpenShift 3.7 to use the User rules check. > > clusterroles.rbac.authorization.k8s.io "admin" is forbidden: User > "system:serviceaccount:automation-broker:automation-broker" cannot get > clusterroles.rbac.authorization.k8s.io at the cluster scope > > > > > > > > > > On Wed, Nov 7, 2018 at 10:19 PM Charles Moulliard > wrote: > >> > >> Hi > >> > >> I'm trying to install OAB on k8s v1.11 according to the info reported > here [1] and that fails as the k8s service catalog can't access the broker > [2] > >> > >> Can OAB be deployed on k8s ? Is there a workaround ? > >> > >> [1] > https://blog.openshift.com/automation-broker-discovering-helm-charts/ > >> [2] https://goo.gl/8F3WxV > >> > >> 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 dzager at redhat.com Thu Nov 8 16:30:32 2018 From: dzager at redhat.com (David Zager) Date: Thu, 8 Nov 2018 11:30:32 -0500 Subject: [Ansible-service-broker] Can OAB be deployed on k8s ? In-Reply-To: References: Message-ID: It appears that the "latest" automation-broker-apb image is using a 3.10 broker image. That would cause the scenario you mention: [2018-11-08T05:18:28.93Z] [DEBUG] - Creating k8s apiserver [2018-11-08T05:18:28.932Z] [ERROR] - Unable to retrieve cluster roles rules from cluster You must be using OpenShift 3.7 to use the User rules check. clusterroles.rbac.authorization.k8s.io "admin" is forbidden: User "system:serviceaccount:automation-broker:automation-broker" cannot get clusterroles.rbac.authorization.k8s.io at the cluster scope I will first verify that updating the images to the latest broker fixes the issue, update the "latest" automation-broker-apb, and add a comment to the blog post. One caveat, it appears there are 251 bundles when the helm adapter is enabled and looking at all of the stable helm charts. The startup sequence for the broker will take some time and it may be better to: 1. wait_for_broker: false 2. broker_probe_initial_delay: 300 I'll be sure to add these notes in any comment/update I make to the blog post. On Thu, Nov 8, 2018 at 10:43 AM Shawn Hurley wrote: > Which version of the automation broker are you using and how are you > deploying? I think you will probably want to look into either the 1. > Auto Escalate config value or 2. The permissions of the > automation-broker that you are granting > > Thanks, > > Shawn Hurley > On Thu, Nov 8, 2018 at 1:10 AM Charles Moulliard > wrote: > > > > When the pod of OAB starts, then this error message appears > > > > [2018-11-08T05:18:28.93Z] [DEBUG] - Creating k8s apiserver > > [2018-11-08T05:18:28.932Z] [ERROR] - Unable to retrieve cluster roles > rules from cluster > > You must be using OpenShift 3.7 to use the User rules check. > > clusterroles.rbac.authorization.k8s.io "admin" is forbidden: User > "system:serviceaccount:automation-broker:automation-broker" cannot get > clusterroles.rbac.authorization.k8s.io at the cluster scope > > > > > > > > > > On Wed, Nov 7, 2018 at 10:19 PM Charles Moulliard > wrote: > >> > >> Hi > >> > >> I'm trying to install OAB on k8s v1.11 according to the info reported > here [1] and that fails as the k8s service catalog can't access the broker > [2] > >> > >> Can OAB be deployed on k8s ? Is there a workaround ? > >> > >> [1] > https://blog.openshift.com/automation-broker-discovering-helm-charts/ > >> [2] https://goo.gl/8F3WxV > >> > >> 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 jmontleo at redhat.com Thu Nov 8 16:48:13 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Thu, 8 Nov 2018 11:48:13 -0500 Subject: [Ansible-service-broker] Can OAB be deployed on k8s ? In-Reply-To: References: Message-ID: <1c2d57c3-994d-9f6b-50fc-fbbb6fc0d4cf@redhat.com> Yes. Again until we get a new oc 3.10 binary with the updated extra vars input format, if we update latest openshift 3.10 will be bust. Use v3.11 / release-1.3. On 11/8/18 11:30 AM, David Zager wrote: > It appears that the "latest" automation-broker-apb image is using a 3.10 > broker image. That would cause the scenario you mention: > > [2018-11-08T05:18:28.93Z] [DEBUG] - Creating k8s apiserver > [2018-11-08T05:18:28.932Z] [ERROR] - Unable to retrieve cluster roles > rules from cluster > ?You must be using OpenShift 3.7 to use the User rules check. > clusterroles.rbac.authorization.k8s.io > ?"admin" is forbidden: > User "system:serviceaccount:automation-broker:automation-broker" cannot > get clusterroles.rbac.authorization.k8s.io > ?at the cluster scope > > I will first verify that updating the images to the latest broker fixes > the issue, update the "latest" automation-broker-apb, and add a comment > to the blog post. > > One caveat, it appears there are 251 bundles when the helm adapter is > enabled and looking at all of the stable helm charts. The startup > sequence for the broker will take some time and it may be better to: > > 1. wait_for_broker: false > 2. broker_probe_initial_delay: 300 > > I'll be sure to add these notes in any comment/update I make to the blog > post. > > On Thu, Nov 8, 2018 at 10:43 AM Shawn Hurley > wrote: > > Which version of the automation broker are you using and how are you > deploying? I think you will probably want to look into either the 1. > Auto Escalate config value or 2. The permissions of the > automation-broker that you are granting > > Thanks, > > Shawn Hurley > On Thu, Nov 8, 2018 at 1:10 AM Charles Moulliard > > wrote: > > > > When the pod of OAB starts, then this error message appears > > > > [2018-11-08T05:18:28.93Z] [DEBUG] - Creating k8s apiserver > > [2018-11-08T05:18:28.932Z] [ERROR] - Unable to retrieve cluster > roles rules from cluster > >? You must be using OpenShift 3.7 to use the User rules check. > > clusterroles.rbac.authorization.k8s.io > "admin" is > forbidden: User > "system:serviceaccount:automation-broker:automation-broker" cannot > get clusterroles.rbac.authorization.k8s.io > at the cluster scope > > > > > > > > > > On Wed, Nov 7, 2018 at 10:19 PM Charles Moulliard > > wrote: > >> > >> Hi > >> > >> I'm trying to install OAB on k8s v1.11 according to the info > reported here [1] and that fails as the k8s service catalog can't > access the broker [2] > >> > >> Can OAB be deployed on k8s ? Is there a workaround ? > >> > >> [1] > https://blog.openshift.com/automation-broker-discovering-helm-charts/ > >> [2] https://goo.gl/8F3WxV > >> > >> 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 > > > _______________________________________________ > 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 jesusr at redhat.com Tue Nov 13 14:16:06 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 13 Nov 2018 14:16:06 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Every 2 weeks from 10am to 10:30am on Tuesday from Tue Oct 30 to Mon Nov 12 (EDT) (ansible-service-broker@redhat.com) Message-ID: <000000000000595c1a057a8c7505@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 10am to 10:30am on Tuesday from Tue Oct 30 to Mon Nov 12 Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * jesusr at redhat.com - creator * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=Z2M2NWo1YzFtNDY2c242MjFoczM3dG9ocjggYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbThmZjUyMzE3ZjZiYjY5MjhjZWUxZmJlYjZiNTQzNTAzMjc4ZmUxNjY&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: 1670 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1707 bytes Desc: not available URL: From jesusr at redhat.com Tue Nov 13 14:16:06 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 13 Nov 2018 14:16:06 +0000 Subject: [Ansible-service-broker] Updated invitation with note: Automation Broker IRC meeting @ Every 2 weeks from 10am to 10:30am on Tuesday (EST) (ansible-service-broker@redhat.com) Message-ID: <0000000000005a4915057a8c758c@google.com> This event has been changed with this note: "The meeting is at 10am ET which is now 3pm UTC" 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 10am to 10:30am on Tuesday Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * jesusr at redhat.com - creator * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=NGFtYjBiOTh2bWZ0dmJqZ2Y2Z2JtN2U5YnMgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbTE5MDI3YTcyYzUxZjg4YTBlZmUwOWVkYTg2ZmQzOGYyZGRmNDg5YTA&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: 1651 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1688 bytes Desc: not available URL: From cmoullia at redhat.com Fri Nov 16 16:57:27 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Fri, 16 Nov 2018 17:57:27 +0100 Subject: [Ansible-service-broker] Error 403 - User Message-ID: Hi When a serviceInstance is created in a namespace, the OABroker (version 3.11) reports this event's error Error provisioning ServiceInstance of ClusterServiceClass (K8S: "1dda1477cace09730bd8ed7a6505607e" ExternalName: "dh-postgresql-apb") at ClusterServiceBroker "openshift-automation-service-broker": Status: 403; ErrorMessage: ; Description: User does not have sufficient permissions; ResponseError: Do I miss a resource + verb in my cluster role yaml file - https://goo.gl/PMnPnK ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Fri Nov 16 20:07:11 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Fri, 16 Nov 2018 21:07:11 +0100 Subject: [Ansible-service-broker] Error 403 - User In-Reply-To: References: Message-ID: I have created a ticket : https://github.com/openshift/ansible-service-broker/issues/1135 On Fri, Nov 16, 2018 at 5:57 PM Charles Moulliard wrote: > Hi > > When a serviceInstance is created in a namespace, the OABroker (version > 3.11) reports this event's error > > Error provisioning ServiceInstance of ClusterServiceClass (K8S: > "1dda1477cace09730bd8ed7a6505607e" ExternalName: "dh-postgresql-apb") at > ClusterServiceBroker "openshift-automation-service-broker": Status: 403; > ErrorMessage: ; Description: User does not have sufficient > permissions; ResponseError: > > Do I miss a resource + verb in my cluster role yaml file - > https://goo.gl/PMnPnK ? > > Regards > > Charles > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesusr at redhat.com Mon Nov 19 22:14:15 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Mon, 19 Nov 2018 17:14:15 -0500 Subject: [Ansible-service-broker] Error 403 - User In-Reply-To: References: Message-ID: Charles, I added comments to the issue. Sincerely, jesus On Fri, 2018-11-16 at 21:07 +0100, Charles Moulliard wrote: > I have created a ticket : > https://github.com/openshift/ansible-service-broker/issues/1135 > > > On Fri, Nov 16, 2018 at 5:57 PM Charles Moulliard < > cmoullia at redhat.com> > wrote: > > > Hi > > > > When a serviceInstance is created in a namespace, the OABroker > > (version > > 3.11) reports this event's error > > > > Error provisioning ServiceInstance of ClusterServiceClass (K8S: > > "1dda1477cace09730bd8ed7a6505607e" ExternalName: "dh-postgresql- > > apb") at > > ClusterServiceBroker "openshift-automation-service-broker": Status: > > 403; > > ErrorMessage: ; Description: User does not have sufficient > > permissions; ResponseError: > > > > Do I miss a resource + verb in my cluster role yaml file - > > https://goo.gl/PMnPnK ? > > > > 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 Nov 20 06:02:56 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 20 Nov 2018 07:02:56 +0100 Subject: [Ansible-service-broker] Error 403 - User In-Reply-To: References: Message-ID: Many thanks On Mon, Nov 19, 2018 at 11:15 PM wrote: > Charles, > > I added comments to the issue. > > Sincerely, > jesus > > On Fri, 2018-11-16 at 21:07 +0100, Charles Moulliard wrote: > > I have created a ticket : > > https://github.com/openshift/ansible-service-broker/issues/1135 > > > > > > On Fri, Nov 16, 2018 at 5:57 PM Charles Moulliard < > > cmoullia at redhat.com> > > wrote: > > > > > Hi > > > > > > When a serviceInstance is created in a namespace, the OABroker > > > (version > > > 3.11) reports this event's error > > > > > > Error provisioning ServiceInstance of ClusterServiceClass (K8S: > > > "1dda1477cace09730bd8ed7a6505607e" ExternalName: "dh-postgresql- > > > apb") at > > > ClusterServiceBroker "openshift-automation-service-broker": Status: > > > 403; > > > ErrorMessage: ; Description: User does not have sufficient > > > permissions; ResponseError: > > > > > > Do I miss a resource + verb in my cluster role yaml file - > > > https://goo.gl/PMnPnK ? > > > > > > 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 mjudeiki at redhat.com Thu Nov 22 14:40:58 2018 From: mjudeiki at redhat.com (Mangirdas Judeikis) Date: Thu, 22 Nov 2018 14:40:58 +0000 Subject: [Ansible-service-broker] ABP registry change Message-ID: hey guys, very short question. can these values be modified from ASB level for APBs? https://github.com/ansibleplaybookbundle/mediawiki-apb/blob/a65418290cc04ba1643f4984f5790ed22690fc2f/defaults/main.yml#L10 I have configured ASB to pull from the specific registry for Openshift on Azure, but as soon as APB deployment kick in, it tries to pull from registry.redhat.io which is not used at the moment in OSA. Thanks, MJ Error: , compute-000000 Failed to pull image " registry.redhat.io/openshift3/mediawiki:latest": rpc error: code = Unknown desc = Get https://registry.redhat.io/v2/openshift3/mediawiki/manifests/latest: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/articles/3399531 -- MANGIRDAS JUDEIKIS (MJ) Software Engineer - OSA Team Red Hat UK M: +44-(0)-792-0267213 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmadsen at redhat.com Mon Nov 26 19:05:56 2018 From: lmadsen at redhat.com (Leif Madsen) Date: Mon, 26 Nov 2018 14:05:56 -0500 Subject: [Ansible-service-broker] ABP registry change In-Reply-To: References: Message-ID: What does your broker-config look like? That's what is specifying which registry to pull from. You'll need to redeploy the ASB as well after making changes to the broker-config so that they are loaded into the pod. Leif. On Mon, Nov 26, 2018 at 10:11 AM Mangirdas Judeikis wrote: > hey guys, > > very short question. can these values be modified from ASB level for APBs? > > https://github.com/ansibleplaybookbundle/mediawiki-apb/blob/a65418290cc04ba1643f4984f5790ed22690fc2f/defaults/main.yml#L10 > > I have configured ASB to pull from the specific registry for Openshift on > Azure, but as soon as APB deployment kick in, it tries to pull from > registry.redhat.io which is not used at the moment in OSA. > > Thanks, > MJ > > > Error: > , compute-000000 Failed to pull image " > registry.redhat.io/openshift3/mediawiki:latest": rpc error: code = > Unknown desc = Get > https://registry.redhat.io/v2/openshift3/mediawiki/manifests/latest: > unauthorized: Please login to the Red Hat Registry using your Customer > Portal credentials. Further instructions can be found here: > https://access.redhat.com/articles/3399531 > > -- > > MANGIRDAS JUDEIKIS (MJ) > > Software Engineer - OSA Team > > Red Hat UK > > M: +44-(0)-792-0267213 > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -- Leif Madsen | Partner Engineer - NFV & CI NFV Partner Engineering Red Hat GPG: (D670F846) BEE0 336E 5406 42BA 6194 6831 B38A 291E D670 F846 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjudeiki at redhat.com Tue Nov 27 14:05:27 2018 From: mjudeiki at redhat.com (Mangirdas Judeikis) Date: Tue, 27 Nov 2018 14:05:27 +0000 Subject: [Ansible-service-broker] ABP registry change In-Reply-To: References: Message-ID: Hey, Broker config below. The only change is that we point to the old registry for now until we can point to the new one. Our boxes do not yet have new registry credentials placed. So until 4.0 we have to use the old registry. broker-config: | broker: auth: - enabled: false type: basic auto_escalate: false bootstrap_on_startup: true dev_broker: false launch_apb_on_bind: false output_request: false recovery: true refresh_interval: 600s ssl_cert: /etc/tls/private/tls.crt ssl_cert_key: /etc/tls/private/tls.key dao: type: crd log: color: true level: info stdout: true openshift: bearer_token_file: "" ca_file: "" host: "" image_pull_policy: Always keep_namespace: false keep_namespace_on_error: false namespace: openshift-ansible-service-broker sandbox_role: edit registry: - black_list: - .*automation-broker-apb$ name: rh tag: v3.11.43 type: rhcc url: https://registry.access.redhat.com white_list: - .*-apb$ - name: localregistry namespaces: - openshift type: local_openshift white_list: [] On Mon, Nov 26, 2018 at 7:06 PM Leif Madsen wrote: > What does your broker-config look like? That's what is specifying which > registry to pull from. You'll need to redeploy the ASB as well after making > changes to the broker-config so that they are loaded into the pod. > > Leif. > > On Mon, Nov 26, 2018 at 10:11 AM Mangirdas Judeikis > wrote: > >> hey guys, >> >> very short question. can these values be modified from ASB level for APBs? >> >> https://github.com/ansibleplaybookbundle/mediawiki-apb/blob/a65418290cc04ba1643f4984f5790ed22690fc2f/defaults/main.yml#L10 >> >> I have configured ASB to pull from the specific registry for Openshift on >> Azure, but as soon as APB deployment kick in, it tries to pull from >> registry.redhat.io which is not used at the moment in OSA. >> >> Thanks, >> MJ >> >> >> Error: >> , compute-000000 Failed to pull image " >> registry.redhat.io/openshift3/mediawiki:latest": rpc error: code = >> Unknown desc = Get >> https://registry.redhat.io/v2/openshift3/mediawiki/manifests/latest: >> unauthorized: Please login to the Red Hat Registry using your Customer >> Portal credentials. Further instructions can be found here: >> https://access.redhat.com/articles/3399531 >> >> -- >> >> MANGIRDAS JUDEIKIS (MJ) >> >> Software Engineer - OSA Team >> >> Red Hat UK >> >> M: +44-(0)-792-0267213 >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > > > -- > Leif Madsen | Partner Engineer - NFV & CI > NFV Partner Engineering > Red Hat > GPG: (D670F846) BEE0 336E 5406 42BA 6194 6831 B38A 291E D670 F846 > -- MANGIRDAS JUDEIKIS (MJ) Software Engineer - OSA Team Red Hat UK M: +44-(0)-792-0267213 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesusr at redhat.com Tue Nov 27 15:21:48 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 27 Nov 2018 10:21:48 -0500 Subject: [Ansible-service-broker] Automation Broker IRC Meeting 2018-11-27 Message-ID: ======================================== #asbroker: Automation broker IRC meeting ======================================== Meeting started by jmrodri at 15:03:16 UTC. The full logs are available at asbroker/2018/asbroker.2018-11-27-15.03.log.html . Meeting summary --------------- * Attendance (jmrodri, 15:04:08) * News (jmrodri, 15:05:06) * No new news this meeting. We haven't done any new builds of the broker or bundle-lib since October 25. (jmrodri, 15:05:45) * We'll hopefully be cleaning up some of the open issues for release 1.4 (ack OCP 4.0). (jmrodri, 15:06:15) * Previous Actions (jmrodri, 15:07:25) * according to the logs from last meeting we had no new open actions. (jmrodri, 15:07:37) * Bugs/Issues Triage (jmrodri, 15:07:56) * broker issues (jmrodri, 15:08:06) * need apiVersion 2 of ansible servcie broker (jmrodri, 15:08:37) * LINK: https://github.com/openshift/ansible-service-broker/issues/1136 (jmrodri, 15:08:41) * LINK: https://github.com/openshift/ansible-service-broker/issues/1136#issuecomment-441287030 (jmrodri, 15:10:35) * Can't start minishift with ASB (jmrodri, 15:10:54) * LINK: https://github.com/openshift/ansible-service-broker/issues/1137 (jmrodri, 15:10:56) * ACTION: jmrodri take a look at Issue 1137 (jmrodri, 15:12:04) * Creating default "automationbroker" CR results in frozen ASB operator stuck on "injecting owner reference" (jmrodri, 15:12:25) * LINK: https://github.com/openshift/ansible-service-broker/issues/1138 (jmrodri, 15:12:30) * Security error in provision new bundle (jmrodri, 15:13:20) * LINK: https://github.com/openshift/ansible-service-broker/issues/1139 (jmrodri, 15:13:25) * Open Discussion (jmrodri, 15:16:57) * ACTION: jmrodri email ansible-service-broker list to discussion canceling IRC meetings going forward (jmrodri, 15:18:00) Meeting ended at 15:18:04 UTC. Action Items ------------ * jmrodri take a look at Issue 1137 * jmrodri email ansible-service-broker list to discussion canceling IRC meetings going forward Action Items, by person ----------------------- * jmrodri * jmrodri take a look at Issue 1137 * jmrodri email ansible-service-broker list to discussion canceling IRC meetings going forward * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jmrodri (34) * brokerbot` (24) * jmontleon (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From jesusr at redhat.com Tue Nov 27 15:28:08 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 27 Nov 2018 10:28:08 -0500 Subject: [Ansible-service-broker] Discussion: Canceling Automation Broker IRC meetings Message-ID: <56636fabd94facac354294d53baa99b4a4bc1994.camel@redhat.com> As mentioned during today's IRC meeting, the topic of canceling the IRC meetings going forward. The attendance has dropped significantly over the past few months. Today we had 3 attendees: myself, brokerbot and one other person. Last meeting was the same and the meeting before that was just myself and the bot. If you would like to keep the IRC meetings and the reports please respond by December 7th, 2018. Otherwise, I will cancel the IRC meetings beginning with our next meeting scheduled for December 11th, 2018. Sincerely, jesus rodriguez From rhallise at redhat.com Wed Nov 28 14:49:28 2018 From: rhallise at redhat.com (rhallise at redhat.com) Date: Wed, 28 Nov 2018 14:49:28 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Every 2 weeks from 10am to 10:30am on Tuesday (EST) (ansible-service-broker@redhat.com) Message-ID: <0000000000004aa8d0057bbaacc6@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 10am to 10:30am on Tuesday Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * jesusr at redhat.com - creator * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=NGFtYjBiOTh2bWZ0dmJqZ2Y2Z2JtN2U5YnMgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbTE5MDI3YTcyYzUxZjg4YTBlZmUwOWVkYTg2ZmQzOGYyZGRmNDg5YTA&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: 1727 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1766 bytes Desc: not available URL: