Description of problem: In online env,the project admin role name is openshift-online:admin,so on web console,the prompt also should be updated to "oc policy add-role-to-user openshift-online:admin wsun1 -n <projectname>" Version-Release number of selected component (if applicable): dev-preview-int How reproducible: always Steps to Reproduce: 1.Login web cosnole 2.Create a project and then access /console page 3. Actual results: There is prompt "A project admin can add you as an admin to a project by running the command oc policy add-role-to-user admin wsun1 -n <projectname>" Expected results: The prompt should be updated to "A project admin can add you as an admin to a project by running the command oc policy add-role-to-user openshift-online:admin wsun1 -n <projectname>" Additional info:
There is no way for us to know, the right fix is to put in placeholder text like <role> instead of the actual role name. Should also probably update the message to something like "A project admin can add you to a role in a project by running ..."
ose PR for 3.2.0.z branch https://github.com/openshift/ose/pull/188
Checked this bug using the hotfix puddle,the bug has been fixed. Now on the web console ,the prompt is : A project admin can add you to a role on a project by running the command oc policy add-role-to-user <role> wsun -n <projectname> After the fix is merged to Online and the bug is moved to ON_QA,I'll verify it.
This is in atomic-openshift-3.2.0.43-1.git.0.672599f.el7
Checked against atomic-openshift-3.2.0.43-1.git.0.672599f.el7 Now the prompt on web console is: A project admin can add you to a role on a project by running the command oc policy add-role-to-user <role> yapei -n <projectname> yapei is current user
Will change product to Atomic Enterprise Platform and OpenShift Enterprise since issue is not specific to Online and changes already merged in OSE New prompt message is more flexible, user could change <role> based on different envs
Move to VERIFIED since it works as expected now
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/RHSA-2016:1094