-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start OpenShift Origin with service catalog #18288
Comments
I got a different error while trying to reproduce this:
|
It appears this is known issue when redeploying applications using Fabric8 Maven Plugin S2I in OpenShift 3.7. It's yet unknown whether the issue is an maven plugin issue or OpenShift one. The service catalog is not required AFAIK to replicate the issue. |
Verified @galderz are you ok to close this issue? |
@pmorie's error, at least, is caused by using the latest (to be v3.9) oc to provision a previous version of openshift (v3.7.1). It does not work because the server APIs are incompatible between the two versions. See https://bugzilla.redhat.com/show_bug.cgi?id=1530069. Download a v3.7.1 oc from https://github.com/openshift/origin/releases/tag/v3.7.1 then run |
Hmmm, I think something else got on the way, maybe my minikube set up. Anyway, I've stopped using the service catalog since I don't actually need it. |
Hi,
I'm using OpenShift Origin 3.7.1 and I'm getting this error when trying to start with service catalog:
This has started appearing after starting to play with minishift and minikube for other projects. Do you know what could be causing this or how to workaround it?
I have
kubectl
1.7.12 in the path when using OpenShift Origin 3.7.1. I'm wondering if my minikube installation is getting the way? Or is there some other problem? How to debug this further?Cheers,
Galder
The text was updated successfully, but these errors were encountered: