Bug 1784725
| Summary: | Console should do special character check when create routing labels | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | shahan <hasha> |
| Component: | Management Console | Assignee: | David Taylor <dtaylor> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aos-bugs, dtaylor, jokerman, yanpzhan |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Create an Alertmanager Receiver, enter "#@$#$%" into a routing label key.
Consequence: The receiver will be created, but get an AlertmanagerFailedReload Alert: "Reloading Alertmanager's configuration has failed for openshift-monitoring/alertmanager-main-x."
Fix: Added form field validation to Create Receiver form.
Result: Now when entering "#@$#$%" into a routing label key there is an field error message: "Invalid name". There is also an info in tooltip: "Label name must not begin with a digit and contain only alphanumeric characters or '_'.". Once cannot save the form until "#@$#$%" is removed from the routing label key/name.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-04 11:20:24 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: | |||
|
Description
shahan
2019-12-18 07:48:41 UTC
Tested on ocp 4.4 env with payload 4.4.0-0.nightly-2020-02-12-191550. Create alertmanager receiver, set routing label key with: #@$#$%, there will be info: Invalid name, and there is info in tooltip: Label name must not begin with a digit and contain only alphanumeric characters or '_'. The bug is 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-2020:0581 |