Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ghost opened this issue Sep 4, 2018 · 2 comments
Open

Comments

@ghost
Copy link

ghost commented Sep 4, 2018

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 -

@ghost ghost changed the title How long does it take for a new local apb to show up in the catalog UI How long should it take for a new local apb to show up in the catalog UI Sep 4, 2018
@Asgoret
Copy link

Asgoret commented Nov 26, 2018

You can change it in ASB config. Relist value is 600s (default). I put in 10s and work good) but i refresh and sync manul for speed up this process

@Asgoret
Copy link

Asgoret commented Nov 26, 2018

@eivantsov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant