Bug 1321048
Summary: | 1B: Can modify Environment Path label such that creation fails | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Quickstart Cloud Installer | Reporter: | Matt Reid <mreid> | ||||||
Component: | WebUI | Assignee: | jmagen <jmagen> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Tasos Papaioannou <tpapaioa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 1.0 | CC: | ernelson, jmatthew, smallamp, tcarlin, tpapaioa | ||||||
Target Milestone: | ga | Keywords: | Triaged | ||||||
Target Release: | 1.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2016-09-13 16:27:28 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: | 1342594 | ||||||||
Attachments: |
|
Description
Matt Reid
2016-03-24 14:32:25 UTC
Created attachment 1139999 [details]
Error message when label prevents the creation of a new environment path
Created attachment 1140000 [details]
After the error, the bad Label persists when you reopen the New Environment Path dialog
Already fixed, label field has been disabled. The logic for lifecycle environment names and labels on 1B. Update Availability is inconsistent with the logic used under the Satellite's Content > Lifecycle Environments tab. 1.) If I create a new environment under Content > Lifecycle Environments > New Environment Path, I can use spaces and punctuation marks. The label replaces them with underscores. For example: Name: Fusor<space>environment<space>1,<space>for<space>fun! Label: Fusor_environment_1__for_fun_ If I try to create the same name under 1B. Update Availability > After manually publishing them > New Environment Path, I get the warning message after typing the first 'e': Name: Fusor<space>e -> This field must contain only 'A-Z', 'a-z', '0-9', '_' or '-' characters. 2.) If I create an environment under Content > Lifecycle Environments, any leading or trailing spaces I enter in the name are trimmed from the name and label. They get trimmed from the name, but not from the label, when creating the environment in 1B. Update Availability. For example, entering a name of "<space>test<space>" generates a label of "test" in Content > Lifecycle Environments, and a label of "_test_" in 1B. Update Availability. 3.) 1B. Update Availability generates a label with all letters lowercased, but Content > Lifecycle Environments. E.g., an environment name of "Test" gets a label of "test" in the former, but "Test" in the latter. QCI-1.2-RHEL-7-20160718.t.0 None of the issues in https://bugzilla.redhat.com/show_bug.cgi?id=1321048#c4 have been fixed in QCI-1.2-RHEL-7-20160718.t.0. Tasos, try again please. Maybe you were on a system where the commit was not merged. I just tried again and it seems fixed on my system. The fixes are in QCI-1.2-RHEL-7-20160720.t.0. Marking as 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/RHEA-2016:1862 |