Because we are starting regression test in 'Next-Gen Installer' env, tsb&asb operator images are not ready in downstream, so add `TestBlocker` tag to trace.

I saw asb and tsb operator image is exist on brew registry, but not exist in reg-aws registry, can you help push the them to reg-aws registry?

I'm not sure if they need to become a part of the puddles in order for that to happen. We're working on it. I'll be submitting PR's to add the downstream Dockerfiles and creating the individual requests using the ART template today.

We're also still missing ansible-runner-http downstream as far as I can see so these images likely won't work anyway.

We'll upstream image for pre-test, remove testblocker keywords.

In the lastes build: registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-02-12-005016, still no asb and tsb operators:
checking by command: 
oc adm release info --pullspecs "registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-02-12-005016"

Adding TestBlocker and beta2blocker since broker operators should be ship in beta 2 release.

Can you check the other registries again for the TSB operator? From what I was hearing the sync may have just not happened yet.

(In reply to Jason Montleon from comment #17)
> ansible-service-broker-operator should be available now as well. Please let
> us know if the images are available on the registries you expect or if
> something is still preventing you from starting to test these. Thanks!
> 
We can get operator images from downstream registry, remove TestBlocker.

For other cluster operators we get from registry.svc.ci.openshift.org or origin-release.svc.ci.openshift.org.
But I'm not exactly sure which registry the 2 operators SHOULD be placed. 

This may be confirmed with ART team or Release team.

Tim, could you help us understand if we need additional setup to see these images on these registries?

Thanks Luke.

Jason, 
how can we use the downstream image?
payload in marketplace can not be changed, it still using docker.io/automationbroker/automation-broker-operator:v4.0

the ansible-playbook also using docker.io/automationbroker/automation-broker-operator:v4.0 
can you fix the payload in marketplace or seperate to use 2 operators(tsb-operator or asb-operator) and so that we can replace them as workaround ?

@Jason - I think if we are starting to talk about how to test then all the images are downstream and it is on us to figure out how to test.

@Zihan - your correct that this is a problem. I have been working on a solution. Basically, the problem is that we will have to bypass OperatorHub and create our own catalog source for the Broker built with its image and different version of the operator-registry. I will put a doc together today or tomorrow. I believe that there is probably an OperatorHub or OLM bug/feature here that is the underlying cause. Do you think that we could open a bug to track and we can close this out with the workaround?

For downstream image, we still need ways to using the 2 downstream images through marketplace or other workaround which is the last step to verify this bug. 
Move to Modified.

Changing status to Assign since we are still waiting the clarification and downstream images are not ready for test.
Please refer to comment 22 and comment 24. Thanks.

This PR is needed: https://github.com/openshift/ansible-service-broker/pull/1187

To use this Dockerfile:

create a new image from the operator directory. Here is where you can use the build-args for the downstream images. There is no default so you have to enter both to get a build that will work. Example:

$ docker build -t quay.io/shawn_hurley/testing-downstream-catalog-source -f build/olm-testing.Dockerfile --build-arg operator_name=quay.io/shawn_hurley/abo:v4.0 --build-arg broker_name=quay.io/shawn_hurley/ab:v4.0 .

Run this image as a catalog source by creating this resource:

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: abo-registry
  namespace: openshift-operator-lifecycle-manager
spec:
  sourceType: grpc
  image: quay.io/shawn_hurley/testing-downstream-catalog-source
Then follow the same UI steps to install the automation-broker-operator and automation-broker which should use the images that you changed.

NOTE: This is only for testing.

Please note that the downstream process is still being worked on for these images. This is not something that we can change, and I don't think keeping this bug open is worth tracking that IMO. Up to you guys though.

thanks for your workaround create downstream image for testing.

where should we release tsb/asb operators and link to marketplace? 
For other community operators, they temporarily use 'quay.io' for operator image which by default linked to marketplace. 
I'll clone a bug for this.

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