Description of problem: When using the UI or API, the template_sync_prefix has it's value blank space stripped before persistence. The plugin has configured with the value "community " - notice the space at the end. This allows templates that are imported to have the following pattern: community kickstart template community finishing template community kickstart PXELinux template However, upon update with a new prefix (ex: "Company "), the blank space is stripped, and now it looks like this upon import: Companykickstart template Companyfinishing template Comapnykickstart PXELinux template Further, in the UI, it appears the blank space is visible, until you reload the page, then you see the persistence layer has stripped the blank space. Version-Release number of selected component (if applicable): tfm-rubygem-foreman_templates-5.0.1-1.fm1_15.el7sat.noarch How reproducible: Steps to Reproduce: 1. Update template_sync_prefix setting via hammer 2. Update template_sync_prefix via API 3. Update template_sync_prefix via UI Actual results: Value has it's blank space stripped. Expected results: Blank space is preserved. Additional info: [root@sat1 foreman-templates]# ./2_prefix_bug + hammer settings set --name template_sync_prefix --value 'Local ' Setting [template_sync_prefix] updated to [Local] ++ curl -s --user admin:******** 'https://sat1.example.com/api/settings?search=name=template_sync_prefix' ++ jq '{results}[][0].id' + id=168 + data='{"value": "Local "}' + curl -s --user admin:******** https://sat1.example.com/api/settings/168 -X PUT -d '{"value": "Local "}' -H content-type:application/json + jq .value "Local"
Created redmine issue http://projects.theforeman.org/issues/22352 from this bug
Upstream bug assigned to oprazak
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22352 has been resolved.
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-2018:2927