Bug 1610991
| Summary: | [3.7] Provision call failed: deploymentconfigs is forbidden: User cannot get deploymentconfigs in project | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Parees <bparees> |
| Component: | Templates | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED ERRATA | QA Contact: | Dongbo Yan <dyan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.7.0 | CC: | aos-bugs, bparees, chezhang, dapark, hgomes, jiazha, jmatthew, jokerman, mmariyan, mmccomas, nick, sdehn, wzheng, xiuwang, zhsun, zitang |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 3.7.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Groups associated w/ a user were not checked when performing access checks to look up the readiness of objects created by the templates.
Consequence: For objects the user could only access due to their group membership, objects would be created by the template, but could not be checked for readiness, resulting in a readiness failure at the template instance level.
Fix: Pass the user's groups when performing the readiness check operation, not just when performing the object creation.
Result: Objects can successfully be checked for readiness as long as the user's group membership permits the check.
|
Story Points: | --- |
| Clone Of: | 1562527 | Environment: | |
| Last Closed: | 2018-08-29 11:39:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1562527, 1610994, 1610995 | ||
| Bug Blocks: | |||
|
Comment 1
Ben Parees
2018-08-02 17:16:16 UTC
Test with # openshift version openshift v3.7.62 kubernetes v1.7.6+a08f5eeb62 etcd 3.2.8 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 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:2547 |