search

ansibleplaybookbundle / ansible-playbook-bundle

THIS REPO IS MIGRATING: https://github.com/automationbroker/apb
GNU General Public License v2.0
140 stars 70 forks source link

APB Push, no image to pull #241

Closed jonnyfiveiq closed 6 years ago

jonnyfiveiq commented 6 years ago

After pushing to the catalog as follows;

$ apb push version: 1.0 name: miqfisherprice description: My first demo app to show the provision of new user in ManageIQ bindable: False async: optional metadata: displayName: FisherPrice User Demo plans:

Finished writing dockerfile. Building APB using tag: [172.30.1.1:5000/openshift/miqfisherprice] Successfully built APB image: 172.30.1.1:5000/openshift/miqfisherprice Pushing the image, this could take a minute... Successfully pushed image: 172.30.1.1:5000/openshift/miqfisherprice Contacting the ansible-service-broker at: https://asb-1338-ansible-service-broker.192.168.64.26.nip.io/ansible-service-broker/v2/bootstrap Successfully bootstrapped Ansible Service Broker Successfully relisted the Service Catalog

When I order the service the service is left in a pending state with the following;

Status : Image Pull Back-off Waiting (ImagePullBackOff)

I have tried "docker push 172.30.1.1:5000/openshift/miqfisherprice" to manually push the image into the registry but this made no difference.

thanks

jonnyfiveiq commented 6 years ago

dsfasfdfdg

dymurray commented 6 years ago

@jonnyfiveiq This looks like it is due to the image name used in the deployment config. You must specify the full name of the image including the registry path. This appears to be searching the default registry paths for just miqfisherprice. Can you please paste your deploymentconfig?

Can you also paste the output of oc get images | grep miq to ensure the image is in the registry?

jonnyfiveiq commented 6 years ago

$ oc get images | grep miq sha256:7f51bf002fca006b6b99345b0d9b3ec99d293d5173b7da942942a58e2763ca34 172.30.1.1:5000/openshift/miqfisherprice@sha256:7f51bf002fca006b6b99345b0d9b3ec99d293d5173b7da942942a58e2763ca34

$ apb list | grep miq returns nothing.....its not in the list.

oc login -u developer -p developer Login successful.

apb push

Building APB using tag: [172.30.1.1:5000/openshift/miqfisherprice] Successfully built APB image: 172.30.1.1:5000/openshift/miqfisherprice Pushing the image, this could take a minute... Successfully pushed image: 172.30.1.1:5000/openshift/miqfisherprice Contacting the ansible-service-broker at: https://asb-1338-ansible-service-broker.192.168.64.27.nip.io/ansible-service-broker/v2/bootstrap Successfully bootstrapped Ansible Service Broker Successfully relisted the Service Catalog

thanks

dymurray commented 6 years ago

@jonnyfiveiq I think I know what the problem is. Your broker config that you showed me in the other issue will not bootstrap APBs from the internal registry unless it passes the whitelist requiring all names to end in -apb. Please change the name of the APB from miqfisherprice to miqfisherprice-apb and rerun apb push. I think this will at the least display the APB in apb list.

dymurray commented 6 years ago

@jonnyfiveiq if you are on IRC and still having trouble feel free to ping me on FreeNode #asbroker.

jonnyfiveiq commented 6 years ago

Thanks @dymurray you are correct....the name must contain APB, otherwise strange results..I have managed one successful test, as soon as I added the suffix -APB to my name in apb.yaml. I will keep playing, but it looks like this may have been the issue here. thanks

jonnyfiveiq commented 6 years ago

defo close this, you must put -apb in the name. though I would expect the apb build or push to do/capture this. thanks

tsanders-rh commented 6 years ago

Yes, I agree....the tooling should be more helpful in this scenario. This is only because currently the default whitelist filter in the broker config is: "-apb"; which could be changed if you don't want to change the name. We are looking at relaxing this default for development installs to "".

On Thu, Mar 8, 2018 at 12:46 PM, John Hardy notifications@github.com wrote:

defo close this, you must put -apb in the name. though I would expect the apb build or push to do/capture this. thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/issues/241#issuecomment-371566302, or mute the thread https://github.com/notifications/unsubscribe-auth/ACAZiUGoHWvJKOLCkW643xfryTFTKj02ks5tcW6OgaJpZM4Sijpl .

-- Todd Sanders Director, Software Engineering Red Hat Inc.