Description of problem: Starting pipelines from web ui and using users with "@" character in the name will fail with this error: >Error "Invalid value: "username": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')" for field "metadata.labels". Version-Release number of selected component (if applicable): Openshift Container Platform 4.5 OpenShift Pipelines Operator 1.0.1 Actions How reproducible: 100% reproducible Steps to Reproduce: 1. Create a pipeline 2. Try to start the pipeline from web UI by user that has "@" character in the name Actual results: Error "Invalid value: "username": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')" for field "metadata.labels". Expected results: It should start Additional info: It prevents users in clusters that use google identity provider, or in general any user with "@" character in the name, to start pipelines.
*** Bug 1876547 has been marked as a duplicate of this bug. ***
Created attachment 1717186 [details] Users with "@" character in their names can't start pipelines from web UI
Verify on build version: 4.6.0-0.ci-2020-09-26-121704 Browser version: Chrome 84
Is this being backported to 4.5?
@sgarciam Yup, we have already had it merged in 4.5.z-stream. It's the linked "Blocks" ticket here: https://bugzilla.redhat.com/show_bug.cgi?id=1883342
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 (OpenShift Container Platform 4.6 GA Images), 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:4196
Thanks for pointing me to the 4.5 link.