Bug 1279781 - Validation Error for Parameter value is not clearly displayed in Host page.
Summary: Validation Error for Parameter value is not clearly displayed in Host page.
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: Nightly
Hardware: Unspecified
OS: Unspecified
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2015-11-10 09:50 UTC by Jitendra Yejare
Modified: 2019-09-26 18:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-12-26 12:58:36 UTC
Target Upstream Version:

Attachments (Terms of Use)
Screenshot Attached. (251.41 KB, image/png)
2015-11-10 09:50 UTC, Jitendra Yejare
no flags Details
validation message displayed correctly (9.34 KB, image/png)
2016-12-26 12:58 UTC, Tomer Brisker
no flags Details

Description Jitendra Yejare 2015-11-10 09:50:38 UTC
Created attachment 1092147 [details]
Screenshot Attached.

Description of problem:
A validation error for invalid value to parameter is not displayed clearly in Host-> Parameter tab specially in red colour as it does in Puppet class parameter.

First of all I thought there is no Error only. But later realized that its there but not clear.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Override a puppet class parameter in Host->Parameters tab.
2. Set the invalid value for parameter.
3. Observe the Error dialog for invalid value.

Actual results:
The error dialog displayed but its not clear enough. Displays in Gray colour looks faint.

Expected results:
The error dialog should be clearly visible and should be in Red Colour.

Additional info:

Comment 2 Bryan Kearney 2016-07-08 20:48:36 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 4 Tomer Brisker 2016-12-26 12:58:21 UTC
Created attachment 1235390 [details]
validation message displayed correctly

This works correctly in Satellite 6.2.6. Closing.

Note You need to log in before you can comment on or make changes to this bug.