Red Hat Bugzilla – Bug 1284781
Smart variable with space in its name allowed to create. Actually It should not.
Last modified: 2016-07-27 07:22:27 EDT
Created attachment 1098065 [details]
Description of problem:
Smart Variable with space in its name allowed to create in a puppet class. Which should not be allowed.
And also after creating the smart variable, it is not viewable, editable and deletable too.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to create a smart variable with name having blank space, from Config -> Classes -> Class -> Smart Variables tab.
Smart Variable with space in its name allowed to create in a puppet class.
1.Smart Variable with space in its name should not be allowed to create in a puppet class.
2. There should be a proper error message displayed saying space not allowed in variable name.
Connecting redmine issue http://projects.theforeman.org/issues/12577 from this bug
Upstream bug component is Provisioning
Upstream bug assigned to email@example.com
Moving to POST since upstream bug http://projects.theforeman.org/issues/12577 has been closed
Applied in changeset commit:54188a7c45c79df42387cba7025b2e7f9a3fbe2a.
This issue is still reproducible in upstream.
Build : foreman-1.11.0-0.develop.201601251557git59dc77b.el6.noarch
The issue is reproducible in latest Satellite 6.2 snap 3.
I can create a smart var with blank space in it and also after creating the smart var is not view-able, editable, delatable from Configure -> Classes -> class -> Smart variable.
The smart variable won't be saved, the issue here is that you can't see the validation message.
I created another upstream issue for the hidden validation: http://projects.theforeman.org/issues/14183.
Created attachment 1159463 [details]
[Verified] Screenshot Attached
@Sat 6.2 Snap 11
While adding/updating a smart variable with white space in key name, the error shown as "Can't contain spaces.". This is an expected behavior.
The verification Screenshot attached.
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.