Bug 1156605
Summary: | Admin member in domain could not view the team in the same domain | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
Component: | Management Console | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.2.0 | CC: | adellape, cryan, ffranz, jliggitt, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, wsun, yanpzhan |
Target Milestone: | --- | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-openshift-origin-console-1.32.1.1-1 | Doc Type: | Bug Fix |
Doc Text: |
Previously, after adding a team as a "view" member to a domain, "admin" members for the same domain could not view the team in the Management Console. This bug fix updates the Management Console to address this issue, and as a result "admin" members of a domain can now view teams that are a member of the same domain in the Management Console.
|
Story Points: | --- |
Clone Of: | 1156374 | Environment: | |
Last Closed: | 2014-12-10 13:24:41 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: | 1156374 | ||
Bug Blocks: |
Description
Brenton Leanhardt
2014-10-24 18:23:39 UTC
Verified on ose2.2/2014-11-26.3 Steps to verify: 1.Log in website with account1 2.Create a team named team1 3.Add team1 as view member to domain(domain1) 4.Add another user(account2) as admin member to the same domain(domain1) 5.Log in website with account2 6.Access app/console/domain/domain1 7.Click "team1" 8.Click "View this team" Actual results: 8.Could view the team1 page with member info containing account1. 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://rhn.redhat.com/errata/RHBA-2014-1979.html |