Bug 1324632 - Smart variable not showing whitespace validation
Summary: Smart variable not showing whitespace validation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: orabin
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1284781
TreeView+ depends on / blocked
 
Reported: 2016-04-06 20:25 UTC by Bryan Kearney
Modified: 2019-09-26 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:39:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
[Verified] Screenshot Attached (68.18 KB, image/png)
2016-05-19 12:46 UTC, Jitendra Yejare 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14183 0 None None None 2016-04-22 15:00:10 UTC

Description Bryan Kearney 2016-04-06 20:25:09 UTC 
Since to_param uses the key as is with whitspace the view can get links to smart variables that contain whitespace and that won't allow to click them and see the error e.g: href="#1450-my key".
Comment 1 Bryan Kearney 2016-04-06 20:25:11 UTC 
Created from redmine issue http://projects.theforeman.org/issues/14183
Comment 2 Bryan Kearney 2016-04-06 20:25:14 UTC 
Upstream bug assigned to orabin
Comment 3 Bryan Kearney 2016-04-06 22:08:09 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14183 has been closed
-------------
Ori Rabin
Applied in changeset commit:ea740cfed3ee43f80095dce087065ec0fe8c9231.
Comment 4 Jitendra Yejare 2016-05-19 12:46:40 UTC 
Created attachment 1159464 [details]
[Verified] Screenshot Attached
Comment 5 Jitendra Yejare 2016-05-19 12:46:56 UTC 
Verified !
@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.
Comment 6 Bryan Kearney 2016-07-27 11:39:47 UTC 
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:1501
Note You need to log in before you can comment on or make changes to this bug.