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

Pushing to broker on minishift rejected #201

Closed cunningt closed 6 years ago

cunningt commented 6 years ago

Trying to use the apb tool to push to the broker on minishift - I haven't had luck with push without the -o or with --secure either. I've tried logging in through oc as developer, system, and admin, and none of those options seem to work.

tcunning@tcunning-OSX:/tmp/my-test-apb$ apb push -o version: 1.0 name: my-test-apb description: This is a sample application generated by apb init bindable: False async: optional metadata: displayName: my-test plans:

Failed to find registry service IP address. Exception occurred! Unable to get registry IP from namespace default

STEPS TO REPRODUCE -

Install the minishift addon (https://github.com/sabre1041/cdk-minishift-utils) Start minishift - MINISHIFT_ENABLE_EXPERIMENTAL=y minishift start --openshift-version=v3.7.0 --service-catalog --memory 4GB

You should see the ASB deployed at the end of your startup log - -- Applying addon 'ansible-service-broker':....... Ansible Service Broker Deployed

Configure apb tool (see ansible-playbook-bundle directions) apb init my-test-apb cd my-test-apb apb prepare apb build apb push -o / apb push --secure / apb push (I may be doing something wrong here in this step, but I'm not sure what)

dymurray commented 6 years ago

Hey Tom,

With the latest RPM build (as of in the last hour) apb push -o no longer exists. We removed this to end confusion between the two ways one could "push" an APB.

You need to be logged in as a cluster-admin user on OCP that has a valid auth token (oc whoami -t and cannot be system:admin). Assuming you are logged in, you can then just do apb push which will push the container image to the openshift namespace. We fixed a good amount of bugs in the last release so if you can update and try again we might get a better error message.

rthallisey commented 6 years ago

@cunningt if you're still seeing the same issue after you do what @dymurray mentioned above then please re open the issue.