Cause: Less than (<) and greater than (>) characters are valid within project display names, but inclusion of them in a way that mimics html (e.g., <displayname>) results in display names that do not appear in the choose existing project dropdown on the create from URL page.
Consequence: Project display names that look like html do not appear in the choose existing project dropdown on the create from URL page.
Fix: Escape < and > characters as HTML entities so that they display properly.
Result: Strings that looks like HTML are now properly escaped and display as strings.
Created attachment 1242018[details]
display name is <my display name>
Description of problem:
Create a project with display name in angle brackets like "<my display name>". Go to external page like https://xxx:8443/console/create?tab=fromCatalog&name=nodejs-ex&imageStream=nodejs&imageTag=4. Click drop down list and the project "<my display name>" is missing
Version-Release number of selected component (if applicable):
v3.5.0.5+8f2840d
How reproducible:
Always
Steps to Reproduce:
1. Create a project with: *name is "myproject", *Display Name is "<my display name>"
2. Go to external page to create app:
Eg. https://xxx:8443/console/create?tab=fromCatalog&name=nodejs-ex&imageStream=nodejs&imageTag=4
3. From "Choose Existing Project" drop down list, check the projects
4. Create another project with: *name is "myproject", *Display Name is "my <display name>"
5. Go to the external page by step2 and check the drop down list again
Actual results:
3. Content inside angle brackets is missing.
5. The "<display name>" is missing from the drop down list, only left "my", the new created project is actually exist.
Please see the screenshot.
Expected results:
3&5. Content inside angle brackets should be shown.
Additional info:
Checked on OCP v3.5.0.14, create projects with Display Name "<my display name>" and "my <display name>", when create app from external page, all project are list correctly in "Choose Existing Project" drop down list and can be chosen.
The bug has been fixed, so move it to Verified.
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-2017:0884