Skip to content

How long should it take for a new local apb to show up in the catalog UI #319

@ghost

Description

Perhaps, I am missing smth, but what I have done is:

  1. Configured timeout in cm, so that the catalog is bootstrapped every minute
  2. Pushed an image to an internal registry, openshift tnamespace
  3. In logs, I can see my apb
time="2018-09-04T05:37:47Z" level=debug msg="spec '63d8302ad52da8345b50173a0e745212\|localregistry-code-ready-apb' needs to be updated"

and eventually

time="2018-09-04T05:37:59Z" level=info msg="update spec: 63d8302ad52da8345b50173a0e745212\|localregistry-code-ready-apb to crd"
...

time="2018-09-04T05:38:04Z" level=info msg="Broker successfully bootstrapped" 

However, it takes up to 5 mins for a new apb to show up in the catalog UI. This makes development and debugging cycle quite long.

Origin 3.9 (oc cluster up)
Installed ansible automation catalog via curl https://raw.githubusercontent.com/openshift/ansible-service-broker/master/apb/install.yaml | oc create -f -

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions