Bug 1840812

Summary: When user names contain a '#' in their name, the console cannot display the user resource
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.zCC: aos-bugs, jokerman, spadgett, yanpzhan
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the web console would not let you view user details when the username contained special characters such as '#'. The console now lets you see the user details regardless of special characters in the name.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-23 00:57:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1835460    
Bug Blocks: 1851485    

Description OpenShift BugZilla Robot 2020-05-27 16:26:33 UTC
+++ This bug was initially created as a clone of Bug #1835460 +++

Created attachment 1688199 [details]
result of navigating to a user with #

Description of problem:
In IBM public cloud, user names are of the format: name#domain
When trying to display a user through the console, you get a (404) Not Found error.

Version-Release number of selected component (if applicable):
3.4.18

How reproducible:
Always

Steps to Reproduce:
1. Create a username that contains '#'
2. Navigate in the console to the user

Actual results:
You get a 404 not found

Expected results:
The user information is displayed

Comment 1 Samuel Padgett 2020-05-28 13:56:19 UTC
status: PR ready, waiting for cherry-pick-approved label

Comment 4 Yanping Zhang 2020-06-11 14:46:59 UTC
Checked on ocp 4.4 cluster with payload 4.4.0-0.nightly-2020-06-11-064343
Create a user "user#test1", and the user has ever login via client.
On console, go to the user's detail page, the page displays well.
The bug is fixed.

Comment 6 errata-xmlrpc 2020-06-23 00:57:26 UTC
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-2020:2580