no matches for servicecatalog.k8s.io

[megian]

Version

oc v3.7.0+7ed6862
kubernetes v1.7.6+a08f5eeb62
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://master1:8443
openshift v3.7.0+7ed6862
kubernetes v1.7.6+a08f5eeb62

Steps To Reproduce

ansible-playbook -i hosts playbooks/byo/openshift-cluster/service-catalog.yml

Current Result

TASK [ansible_service_broker : Create the Broker resource in the catalog]
fatal: [master1]: FAILED! => {"changed": false, "failed": true, "msg": {"cmd": "/usr/local/bin/oc create -f /tmp/brokerout-2AWk1W -n default", "results": {}, "returncode": 1, "stderr": "error: unable to recognize "/tmp/brokerout-2AWk1W": no matches for servicecatalog.k8s.io/, Kind=ClusterServiceBroker\n", "stdout": ""}}

Expected Result

no error

[cscetbon]

@megian Can you tell me why you closed this issue. I got the same error. Even using catalog instead of servicecatalog doesn't help

[megian]

The issue is still open, but i guess more an openshift-ansible issue. That's why I created another issue here: openshift/openshift-ansible#6377

[cscetbon]

Okay I see. I have the same issue with minikube :(

[megian]

Reopen the issue, because it seams not only to be openshift-ansible related.

[bortek]

Same issue here, any progress ?

[megian]

It seams to occur, if there is no StorageClass defined, asb-etcd in the namespace openshift-ansible-service-broker is waiting for permanent storage and does fail. This causes asb to fail and adding the resource is not possible.

[openshift-bot]

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

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close