Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

Upstream bug component is Discovery Plugin

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16657 has been resolved.

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.

Created attachment 1311014 [details]
Discovery rule creation name limit to 255 char

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