Bug 1378486

Summary: No validation for Discovery Rule name
Product: Red Hat Satellite Reporter: Oleksandr Shtaier <oshtaier>
Component: Discovery PluginAssignee: Swapnil Abnave <sabnave>
Status: CLOSED ERRATA QA Contact: Amit Karsale <akarsale>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3.0CC: akarsale, bbuckingham, jcallaha, sabnave
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Discovery rule creation name limit to 255 char none

Description Oleksandr Shtaier 2016-09-22 14:05:28 UTC
Description of problem:
When I try to create or update Discovery Rule with name that is longer than 255 characters, I got no error anymore as I had for 6.2.x


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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Discovery rule is created successfully

Expected results:
Error message ("is too long (maximum is 255 characters)") is displayed

Additional info:

Comment 3 Bryan Kearney 2016-09-22 18:19:54 UTC
Upstream bug component is Discovery Plugin

Comment 4 Bryan Kearney 2016-10-12 10:02:31 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16657 has been resolved.

Comment 5 Amit Karsale 2017-08-09 06:35:29 UTC
the issue is been verified on snap9 Satellite 6.3 beta release and is working as expected. Please find the attachment below for further verification.

Comment 6 Amit Karsale 2017-08-09 06:36:22 UTC
Created attachment 1311014 [details]
Discovery rule creation name limit to 255 char

Comment 7 Satellite Program 2018-02-21 16:54:17 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/RHSA-2018:0336