Error: Attempt to list APBs in the broker returned status: 503

Question

Error: Attempt to list APBs in the broker returned status: 503

fmontaldo3 opened this issue 6 years ago · 4 comments

This form is for bug reports and feature requests. Major features will go through a spec process.

Feature: apb list

Bug: Error: Attempt to list APBs in the broker returned status: 503

What happened:
After the configuration of minishfit to anelabe addons for ansible-service-broker I can't run apb list

[fmontaldo@arofflab01 add-ons]$ apb list
Contacting the ansible-service-broker at: https://asb-1338-ansible-service-broker.192.168.42.24.nip.io/openshift-automation-service-broker/v2/catalog
Error: Attempt to list APBs in the broker returned status: 503
Unable to list APBs in Ansible Service Broker.

my config

export MINISHIFT_ENABLE_EXPERIMENTAL=y
minishift start --service-catalog --disk-sixe=300G --memory=12G

[fmontaldo@arofflab01 scripts]$ minishift start --service-catalog --disk-size=300G --memory=12G
-- Starting profile 'minishift'
-- Checking if requested OpenShift version 'v3.9.14' is valid ... OK
-- Checking if requested OpenShift version 'v3.9.14' is supported ... OK
-- Checking if requested hypervisor 'kvm' is supported on this platform ... OK
-- Checking if KVM driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-kvm ...
Checking driver binary is executable ... OK
-- Checking if Libvirt is installed ... OK
-- Checking if Libvirt default network is present ... OK
-- Checking if Libvirt default network is active ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting local OpenShift cluster using 'kvm' hypervisor ...
-- Minishift VM will be configured with ...
Memory: 12 GB
vCPUs : 2
Disk size: 300 GB
-- Starting Minishift VM .................. OK
-- Registering machine using subscription-manager
Red Hat Developers or Red Hat Subscription Management (RHSM) username: fmontaldo3@gmail.com
Red Hat Developers or Red Hat Subscription Management (RHSM) password: [HIDDEN]
Registration in progress ........... OK [23s]
-- Checking for IP address ... OK
-- Checking for nameservers ... OK
-- Checking if external host is reachable from the Minishift VM ...
Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 1% used OK
Importing 'registry.access.redhat.com/openshift3/ose:v3.9.14' ................ OK
Importing 'registry.access.redhat.com/openshift3/ose-docker-registry:v3.9.14' ...... OK
Importing 'registry.access.redhat.com/openshift3/ose-haproxy-router:v3.9.14' ....... OK
-- OpenShift cluster will be configured with ...
Version: v3.9.14
Using nsenter mounter for OpenShift volumes
Using 192.168.42.24 as the server IP
Starting OpenShift using registry.access.redhat.com/openshift3/ose:v3.9.14 ...
OpenShift server started.

The server is accessible via web console at:
https://192.168.42.24:8443

You are logged in as:
User: developer
Password:

To login as administrator:
oc login -u system:admin

-- Waiting for persistent volumes to be created ... OK

-- Applying addon 'admin-user':..
-- Applying addon 'anyuid':.
Add-on 'anyuid' changed the default security context constraints to allow pods to run as any user.
Per default OpenShift runs containers using an arbitrarily assigned user ID.
Refer to https://docs.openshift.org/latest/architecture/additional_concepts/authorization.html#security-context-constraints and
https://docs.openshift.org/latest/creating_images/guidelines.html#openshift-origin-specific-guidelines for more information.
-- Applying addon 'xpaas':....................................................................................................
XPaaS OpenShift imagestream and templates installed
See https://github.com/openshift/openshift-ansible/tree/master/roles/openshift_examples/files/examples/v3.7

eval $(minishift docker-env)
eval $(minishift oc-env)

cd /home/fmontaldo/Documents/minishift-addons/add-ons
minishift addons install ansible-service-broker
minishift addons apply ansible-service-broker
oc adm policy add-cluster-role-to-user cluster-admin developer
sudo yum -y remove apb

yum -y install apb

[fmontaldo@arofflab01 add-ons]$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
quay.io/coreos/etcd latest 972b23538f16 3 hours ago 39.4 MB
docker.io/ansibleplaybookbundle/origin-ansible-service-broker latest 07a2bfed6163 3 weeks ago 605 MB
registry.access.redhat.com/openshift3/ose-haproxy-router v3.9.14 349d7ec4bd2f 2 months ago 1.28 GB
registry.access.redhat.com/openshift3/ose-deployer v3.9.14 ba9779c50c5b 2 months ago 1.26 GB
registry.access.redhat.com/openshift3/ose v3.9.14 7dfaa8d4ac4f 2 months ago 1.26 GB
registry.access.redhat.com/openshift3/ose-docker-registry v3.9.14 924f6e950b50 2 months ago 459 MB
registry.access.redhat.com/openshift3/ose-web-console v3.9.14 a0f5a2e23591 2 months ago 489 MB
registry.access.redhat.com/openshift3/ose-service-catalog v3.9.14 6bed82cc1eca 2 months ago 283 MB
registry.access.redhat.com/openshift3/ose-template-service-broker v3.9.14 21ff0aa9c113 2 months ago 294 MB
registry.access.redhat.com/openshift3/ose-pod v3.9.14 e598d93f5abe 2 months ago 209 MB
[fmontaldo@arofflab01 add-ons]$ oc login -u developer
Logged into "https://192.168.42.24:8443" as "developer" using existing credentials.

You have access to the following projects and can switch between them with 'oc project ':

ansible-service-broker

myproject
openshift

Using project "myproject".
[fmontaldo@arofflab01 add-ons]$ apb list
Contacting the ansible-service-broker at: https://asb-1338-ansible-service-broker.192.168.42.24.nip.io/openshift-automation-service-broker/v2/catalog
Error: Attempt to list APBs in the broker returned status: 403
Unable to list APBs in Ansible Service Broker.
[fmontaldo@arofflab01 add-ons]$

Please help me

jmrodri commented 4 years ago

/close

Answer 1 · 2018-05-31T22:14:05.000Z

minishift details

[fmontaldo@arofflab01 add-ons]$ minishift version
minishift v1.15.1+f19ac09
CDK v3.4.0-2
[fmontaldo@arofflab01 add-ons]$ docker version
Client:
 Version:         1.13.1
 API version:     1.26
 Package version: <unknown>
 Go version:      go1.9.2
 Git commit:      94f4240/1.13.1
 Built:           Mon Apr 30 15:45:42 2018
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: <unknown>
 Go version:      go1.8.3
 Git commit:      774336d/1.13.1
 Built:           Tue Feb 20 13:46:34 2018
 OS/Arch:         linux/amd64
 Experimental:    false
[fmontaldo@arofflab01 add-ons]$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.5 (Maipo)
[fmontaldo@arofflab01 add-ons]$

Answer 2 · 2020-09-06T10:14:03.000Z

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Answer 3 · 2020-09-20T01:09:52.000Z

@jmrodri: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.