Bug 1680535

This is depend on https://bugzilla.redhat.com/show_bug.cgi?id=1652419#c25

https://github.com/openshift/ansible-service-broker/pull/1190

Cluster version is 4.0.0-0.nightly-2019-03-19-004004

Install the Automation broker operator and automation broker on the Web console.
Create Automation Broker:
apiVersion: osb.openshift.io/v1alpha1
kind: AutomationBroker
metadata:
  name: ansible-service-broker
  namespace: jian
spec:
  createBrokerNamespace: 'false'
  waitForBroker: 'false'

[jzhang@dhcp-140-18 ocp210]$ oc get pods
NAME                                         READY   STATUS      RESTARTS   AGE
asb-1-deploy                                 0/1     OOMKilled   0          57m
asb-1-s6pfq                                  2/2     Running     0          56m
automation-broker-operator-5b465bbb5-2z2c7   1/1     Running     0          57m

Check the ansibleservicebroker image:
[jzhang@dhcp-140-18 ocp210]$ oc get pods asb-1-s6pfq -o yaml|grep image
    image: docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v4.0

Check its version, this version doesn't contains the fixed PR, not ready for the test. Change status to MODIFIED.
[jzhang@dhcp-140-18 ocp210]$ oc exec asb-1-s6pfq -- asbd --version
Defaulting container name to dashboard-redirector.
Use 'oc describe pod/asb-1-s6pfq -n jian' to see all of the containers in this pod.
1.4.4

Using operator hub to install asb operator, the operator image is still upstream 'docker.io/automationbroker/automation-broker-operator:v4.0' ( depond on https://bugzilla.redhat.com/show_bug.cgi?id=1685458 )

after create CR, default registry is still 'docker.io',

Move to MODIFIED.

Current status is the same with #comment7 , move back to MODIFIED.

I installed the latest green nightly build:  4.1.0-0.nightly-2019-05-03-093152 and then installed Automation Broker Operator and the ASB automation broker.   The asb pods are still using upstream images from docker.io:


# oc describe pod asb-1-6kq69 | grep Image
    Image:         docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v4.0
    Image ID:      
    Image:          docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v4.0
    Image ID:  


The automation-broker-operator image that was installed is also upstream:

     
# oc describe pod automation-broker-operator-65d8f97965-p9l5f | grep Image
    Image:          docker.io/automationbroker/automation-broker-operator:v4.0
    Image ID:       docker.io/automationbroker/automation-broker-operator@sha256:e988379d4436fd64a11117de20f3f2770acf4fe0d5658d353701cc9e34a48806


Moving to ASSIGNED.   If this is something that should show up in a later build than what is available, please move to POST

This is done via the CR. The only way to do this is via the olm example. You will not be able to verify this until the downstream pipeline exits and you can use the UI.

Shouldn't the example CR in the UI use the correct images?  Or we should provide documentation on how to use the correct images?

The CR in the UI should use the correct configuration values. This only works when you are using OLM.

Verified:
ose-ansible-service-broker-operator:v4.1.0-201905051700
ose-ansible-service-broker:v4.1.0-201905051700

 broker-config: |
    registry: [{"auth_type": "secret", "name": "rhcc", "url": "https://registry.redhat.io", "white_list": [".*-apb$"], "auth_name": "asb-registry-auth", "type": "rhcc"}

but it didn't generate "asb-registry-auth" secret automatically by default, will open another bug to trace it.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0758