Created attachment 1415566 [details] screenshot of error 3.9.14-1.git.0.4efa2ca Getting this error when provisioning a simple (ephemeral) mysql instance from the service catalog: Provision call failed: deploymentconfigs "mysql" is forbidden: User "ocpadmin" cannot get deploymentconfigs in project "testing" The 'ocpadmin' user has cluster-admin role. This occurs whether i bind it or not. Screenshot attached... -Nick
What does the following show: oc adm policy who-can get deploymentconfigs -n testing Also, can you attach the output of: oc get clusterrolebindings -o yaml oc get rolebindings -o yaml -n testing
closing this out as i have not been able to reproduce it (on the exact same install i saw it on initially). Chalking it up to the gremlins that seem to come out with disconnected installs. I'll re-open if it happens again. Thanks! -Nick
Which user exactly is having issue with which project exactly ?
Sounds like a service catalog issue at this point.
The error is being set by the Service Broker. John can your team take a look at this?
Looks like this is a bug in the template instance controller itself, fixing here (will need to backport): https://github.com/openshift/origin/pull/20505
Could reproduce this issue as steps in comments #13 with ocp 3.10.14 && 3.11.0-0.10.0
https://github.com/openshift/ose/pull/1383
Test with # openshift version openshift v3.9.41 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.16 Reproduce steps: 1. Login openshift with user1 and create project 2. Create user group and add admin role to group $oc adm groups new testgroup user1 user2 $oc policy add-role-to-group admin testgroup -n testproject 3. Login to the webconsole as user2 4. Using the web console, switch to that testproject and add the httpd service catalog item, click through accepting defaults 5. Check serviceinstance status $oc get serviceinstance $oc describe serviceinstance/httpd-example-v8fpv Actual result: servicesintance is ready move to verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2549