Bug 1835460

Summary: When user names contain a '#' in their name, the console cannot display the user resource
Product: OpenShift Container Platform Reporter: Cesar Wong <cewong>
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, xiaocwan
Target Milestone: ---   
Target Release: 4.5.0   
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-07-13 17:38:37 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:    
Bug Blocks: 1840812    
Attachments:
Description Flags
result of navigating to a user with #
none
Verification screenshot none

Description Cesar Wong 2020-05-13 20:07:30 UTC
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 3 XiaochuanWang 2020-05-28 01:51:24 UTC
Created attachment 1692906 [details]
Verification screenshot

Comment 4 XiaochuanWang 2020-05-28 01:52:15 UTC
Attached the screenshot for refer.
This is fixed on 4.5.0-0.nightly-2020-05-27-202943, it could be Verified.

Comment 5 errata-xmlrpc 2020-07-13 17:38:37 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:2409