Bug 1883342
Summary: | Users with "@" character in their names can't start pipelines from web UI | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Andrew Ballantyne <aballant> |
Component: | Dev Console | Assignee: | Andrew Ballantyne <aballant> |
Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 4.5 | CC: | aballant, aos-bugs, cjerolim, cpassare, dsundqvi, jjanz, karsharm, nmukherj, ppitonak, spathak |
Target Milestone: | --- | ||
Target Release: | 4.5.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
"Started By" is a metadata point added in 4.5 to help track between Trigger starts and manual starts through the UI. This was stored in the K8s "label" field on the PipelineRun.
K8s Labels were used to hold onto the username; however K8s Labels have a very small subset of characters allowed.
Consequence:
Email-based usernames contain "@" which is not a valid K8s Label field value
Fix:
Move the "Started By" over to the K8s Annotation field, which is more freeform and allows for usernames that contain non-label valid characters
Result:
Resolves the issue that prevented the Pipeline from being started if the username was an email address.
|
Story Points: | --- |
Clone Of: | 1868653 | Environment: | |
Last Closed: | 2020-10-26 15:11:50 UTC | Type: | --- |
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: | 1868653, 1882529 | ||
Bug Blocks: |
Comment 3
Gajanan More
2020-10-22 07:37:25 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 (OpenShift Container Platform 4.5.16 bug fix update), 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:4268 |