Description of problem: Puppet class fails loading in UI when the attribute order is created with upper case characters Version-Release number of selected component (if applicable): satellite-6.3.1-3.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. Navigate to the Satellite UI -> Configure -> Classes 2. Select a puppet class -> Smart Class Parameter. Add a new added a new `Prioritize attribute order` with some upper case letters on it. eg., `test_version,GSD-ALL-00-OB_N_ABCDE01`. Add a matcher at the same time with some values. eg., `test_version=4.1.0,GSD-ALL-00-OB_N_ABCDE01=true` in the same UI transaction. 3. Click Submit. Actual results: The order and matcher would be created, but the puppet class cannot be loaded in Satellite UI anymore. Reason: The lookup_keys table changed the order to all lowercase and stored it. The lookup_values table saved the original upper case letters. This caused inconsistency between the tables and broke the UI. Expected results: Either do not allow upper case letters in `Prioritize attribute order` field or save all lower case in lookup_values table too - to keep the data consistent. Additional info:
Created attachment 1455569 [details] puppet class UI error
Created redmine issue https://projects.theforeman.org/issues/24551 from this bug
Upstream bug assigned to orabin
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24551 has been resolved.
ON_QA verified @Satellite 6.6.0 snap 4.0 Steps: 1. Navigate to the Satellite UI -> Configure -> Classes 2. Select a puppet class -> Smart Class Parameter. > check mark on `Default Behavior` 'Override' -> Add a new `Prioritize attribute order` with some upper case letters on it. eg., `test_version,GSD-ALL-00-OB_N_ABCDE01`. Add a matcher at the same time with some values. eg., `test_version=4.1.0,GSD-ALL-00-OB_N_ABCDE01=true` in the same UI transaction. 3. Click Submit. Observation: 1. Saved all lookup_values in lower case. 2. Puppet class loading in UI
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/RHSA-2019:3172