-
Notifications
You must be signed in to change notification settings - Fork 189
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
Server Forbidden Updates To This Resource #119
Comments
Some additional analysis in openshift/cloud-credential-operator#31 (comment) I think it's my PR but I don't understand why. |
A little more info here: openshift/cloud-credential-operator#31 (comment) |
This was not a CVO bug, operators running before Special label: cluster-version-operator/install/0000_00_cluster-version-operator_00_namespace.yaml Line 7 in 93d4eff
/close |
@abhinavdahiya: Closing this issue. In response to this:
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. |
Our quota admission plugin doesn't allow us to create config maps/service accounts without the OpenShift API server. Therefore those resources should be created either when the OpenShift API is running (runlevel 70) or their namespace should have a special label: openshift.io/run-level: "1" openshift/cluster-version-operator#119 (comment)
Not sure what I've got here but this is a CI failure bringing up a cluster, from the CVO pod logs:
More logs available here: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cloud-credential-operator/31/pull-ci-openshift-cloud-credential-operator-master-e2e-aws/158
The text was updated successfully, but these errors were encountered: