Description of problem: "Host Duplicate DMI UUID" value update failed it the string contains leading or trailing space. Version-Release number of selected component (if applicable): 6.10 Snap5 How reproducible: always Steps to Reproduce: 1. install satellite 6.10 with the latest snap. 2. update the value of "Host Duplicate DMI UUID" from empty to ' [kJVsPkOAqY] ' 3. value update failed with error "Oh no! Something went wrong while submitting the form, the server returned the following error: Value must be comma separated" 4- If I remove the space from the string then the value updated successfully. Actual results: "Host Duplicate DMI UUID" value update failed it the string contains leading or trailing space. Expected results: leading and trailing space should be auto-adjusted by UI and update the value. Additional info:
*** Bug 1975709 has been marked as a duplicate of this bug. ***
Please upload the production.log (whenver you see "Oh no! Something went wrong" kind of error)
For the record, there are two issues with the value used in this example. First, it has square brackets, which was probably not intended. The value(s) should be passed as string, the square brackets are there to indicate it's an array of multiple values but should not be added by the user directly. Otherwise the square brackets are considered to be part of the value. User should enter multiple values without these brackets, just separated with the commas, e.g. kJVsPkOAqY,kJVsPkOAqZ or simply kJVsPkOAqY for a single value. Second problem and the reason for the validation error is, there are spaces in the value. Spaces are not automatically trimmed and any of the value can't contain a space. I agree it may be a good improvement to auto-trim spaces in this field but I wouldn't consider it a bug, since the valid UUID values should never contain a space. If we'll add such an improvement, we need to make that work for more settings, currently I found the following with the same behavior * HTTP(S) proxy except hosts * DNS timeout * Ignore interfaces with matching identifier * Exclude pattern for facts stored in satellite * Allowed bootdisk types * Default parameters lookup path * Ansible roles to ignore * OIDC Audience * Trusted hosts Fixing it just for Host Duplicate DMI UUID would make the experience inconsistent and I'd say even worse.
Created redmine issue https://projects.theforeman.org/issues/35251 from this bug
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.
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.