-
Notifications
You must be signed in to change notification settings - Fork 544
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
Operator install plans fail w/repeat count regexp parsing error with OLM 0.8.1+ on OCP 3.11 #735
Comments
@ron1 I would say the kube-apiserver crash is definitely the issue you are running into. @evan merged a fix to OLM's manifests that removes the probable culprit in OLM's case. I would try pulling from master again and re-applying OLM's manifests. |
I successfully deployed the latest OLM from master with the manifest patches below on OCP 3.11.82. I also successfully deployed an etcd-operator CR from the upstream-community-operators CatalogSource built using DockerFile https://github.com/operator-framework/operator-registry/blob/master/upstream-example.Dockerfile. Thanks for your help.
|
@ron1 thanks for being so patient. This really helps us outline the work we need to do to make our upstream easier to use (which is one of our core focuses). |
I'm running OLM ocp/0.8.1+ on OCP 3.11 with the manifest patches below to work-around already reported issues. The patch includes replacement of image coreos/olm with openshift/origin-operator-lifecycle-manager:latest dated 2019-02-28. I'm also using an upstream-community-operators image built 2019-02-28 via https://github.com/operator-framework/community-operators/blob/master/upstream.Dockerfile. The manifest for this installation is also included below. The approach was inspired by the @njhale comment here: #715 (comment). If you have a better way to use latest OLM and upstream-community-operators with OCP 3.11 please let me know.
My attempts to create install plans for couchbase and etcd upstream-community-operators subscriptions fail with the master api stack trace below. Is it possible this issue is related to Kubernetes issue kubernetes/kubernetes#65470 "Invalid regex in OpenAPI validation crashes API server"?
couchbase-subscription manifest
upstream-community-operators operator-registry manifest
ocp/manifests/0.8.1 patch is included below:
The text was updated successfully, but these errors were encountered: