apb does not appear in "apb list" after "apb push -o" about ansible-playbook-bundle HOT 17 CLOSED

I'm wondering if either the broker or the catalog did not properly process the request. Can you post the result of kubectl get clusterserviceclass -o yaml | grep my-test-apb

from ansible-playbook-bundle.

@rthallisey I have the same probem,

and the command returns nothing

from ansible-playbook-bundle.

Same here, the command returns nothing.

from ansible-playbook-bundle.

Can you please paste your broker config?
oc get configmap broker-config ansible-service-broker -o yaml -n ansible-service-broker

I think you are missing the configuration for the local_openshift registry config.

from ansible-playbook-bundle.

Back from the holiday break :). Are you still seeing this @rwsu or @matzew ?

from ansible-playbook-bundle.

I'm seeing a different problem during push:

Found registry IP at: 172.30.1.1:5000
Building image with the tag: 172.30.1.1:5000/openshift/tripleo-k8s-mariadb
Successfully pushed image: 172.30.1.1:5000/openshift/tripleo-k8s-mariadb
https://asb-1338-ansible-service-broker.172.17.0.1.nip.io/ansible-service-broker
Error: Attempt to bootstrap Broker returned status: 503
Unable to bootstrap Ansible Service Broker.

from ansible-playbook-bundle.

I'm having the same problem. apb build and apb push -o seem to work fine but the apb is not listed afterwards and also not visible in the service catalog. @matzew @rwsu have you been able to find a fix?

@dymurray running oc get configmap broker-config ansible-service-broker -o yaml -n ansible-service-broker show a config map for broker-config, but returns Error from server (NotFound): configmaps "ansible-service-broker" not found for ansible-service-broker. So it looks like i'm missing some configuration?

broker-config did not have a registry entry for local_openshift, so i added one (https://github.com/openshift/ansible-service-broker/blob/master/docs/config.md#local-openshift-registry) but i still can't see the apb.

Any ideas?

from ansible-playbook-bundle.

@rwsu regarding the 503 error, can you try to check the asb pod in the ansible-service-broker project in Openshift? Your user should be able to open it from the web console. Is the pod running or are there any errors in it's log?

from ansible-playbook-bundle.

@pb82 It sounds like you might need to redeploy the ASB pod after editing the configmap. Your error above is my fault, the command should just read oc get configmap broker-config -n ansible-service-broker -o yaml. It was looking for a configmap named ansible-service-broker which doesn't exist. Does redeploying the ASB pod help? That will attempt to bootstrap the images in the openshift namespace which apb push -o prepared for us.

from ansible-playbook-bundle.

@dymurray I didn't try redeploying yet but i ran apb bootstrap. That didn't help. However after adding the local registry config i now see an error in the logs of the ansible-service-broker when i push:

 [ERROR] - unable to retrieve image names for registry localregistry - User "system:serviceaccount:ansible-service-broker:asb" cannot list images.image.openshift.io at the cluster scope: User "system:serviceaccount:ansible-service-broker:asb" cannot list all images.image.openshift.io in the cluster (get images)

For now i'm just pushing my apbs to dockerhub, that works fine. But it would be nice to use the local registry.

from ansible-playbook-bundle.

@pb82 You definitely need to redepoy the ASB pod or else it won't pick up on the changes to broker-config. You also need to be logged in as a user who has cluster-admin access. Right now you are logged in as the asb service account (probably because you just ran the script to deploy the broker). First, log in as an admin user (not system:admin because it doesn't have a token) and then redeploy the broker pod: oc deploy --latest asb (in broker namespace). Then do apb push -o and you should see the image there.

from ansible-playbook-bundle.

@dymurray Ok, will give it a try later today and add the results here

from ansible-playbook-bundle.

@rwsu @pb82 let us know if you're still hitting this, but I think the the master branch has the fix.

from ansible-playbook-bundle.

@rthallisey, does https://raw.githubusercontent.com/openshift/ansible-service-broker/master/scripts/run_latest_build.sh
pickup the latest change on master?

I still don't see the apb listed. "apb push -o" returns

Found registry IP at: 172.30.1.1:5000
Building image with the tag: 172.30.1.1:5000/openshift/tripleo-k8s-mariadb
Successfully pushed image: 172.30.1.1:5000/openshift/tripleo-k8s-mariadb
Contacting the ansible-service-broker at: https://asb-1338-ansible-service-broker.172.17.0.1.nip.io/ansible-service-broker/ansible-service-broker/v2/bootstrap
Error: Attempt to bootstrap Broker returned status: 404
Unable to bootstrap Ansible Service Broker.

from ansible-playbook-bundle.

@rwsu yes, that runs the latest broker.

Try and update your apb tool to master. There were a few changes recently and master should fix the .../ansible-service-broker/ansible-service-broker/... double name. Also -o isn't needed anymore in master. The default with no param is now to push to the openshift registry.

Let me know if that fixes it.

from ansible-playbook-bundle.

@rthallisey, I see a different error now. Please see #212. Thanks.

from ansible-playbook-bundle.

@rwsu ok I'll have a look

from ansible-playbook-bundle.