Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
User is able to put invalid items into an array of values for some settings.

there's just a basic input validation, checking whether the value is a valid list, but no check of the actual values:

e.g.
"DNS timeout"	
setting happily accepts array like this:
[5, 10, 15, 20, -10, foo]

"Allowed bootdisk types"
setting happily accepts array like this:
[subnet, full_host, non_existing_type]

there might be more.

Version-Release number of selected component (if applicable):
6.10.0-21.0

Expected results:
some setting-specific input validation should be implemented, if values are expected to be specific, pre-defined keywords (like in "Allowed bootdisk types"), i'd expect a help message, listing all the possible values.

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.