Red Hat Bugzilla – Bug 1273827
Creating smart variable with period or special character makes smart variable not to view, edit and delete.
Last modified: 2016-07-27 04:58:11 EDT
Created attachment 1085086 [details] Screenshot Attached. Description of problem: In Smart Class-> Smart Variables tab, Creating smart variable with name having period or special character makes smart variable not to view, edit and delete. Version-Release number of selected component (if applicable): foreman-1.11.0-0.develop.201510151605git8893c3b.el7.noarch How reproducible: Always Steps to Reproduce: 1. Create a smart variable from tab Configure -> Classes-> smart class -> Smart variables tab with name having period or special character in it. Actual results: Smart variable with period or special character makes smart variable not to view, edit and delete. Expected results: Smart Variable with period or special character should be able to view, edit or delete from Configure -> Classes-> smart class -> Smart variables tab. Additional info: I am able to view, edit or delete the same smart variable(created with period or special characters) from Configure -> Smart Variables.
Connecting redmine issue http://projects.theforeman.org/issues/12231 from this bug
Upstream bug component is Provisioning
Moving to POST since upstream bug http://projects.theforeman.org/issues/12231 has been closed ------------- Anonymous Applied in changeset commit:51c05864e034d229efe4a4673ec85189da60e90c.
Tested this issue in latest upstream. I can create a smart variable with period character and special chars. Is that an expected behaviour ? Build: foreman-1.11.0-0.develop.201601251557git59dc77b.el6.noarch
As per discussion with Dev, To verify this feature we need hammer 0.6 which is not yet available in downstream. (Current Sat 6 snap 7.1)
Verified in Sat 6.2 snap 8.2 I can create, edit and delete a smart variable with special char and period char in Configure -> Classes -> class_name -> Smart Variables. So moving this to 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/RHBA-2016:1500