Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Descriptionsthirugn@redhat.com
2016-04-20 16:06:59 UTC
Description of problem:
Operating system description length accepts more than 255 characters
Version-Release number of selected component (if applicable):
satellite-6.2.0-8.2.beta.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
1.Create an operating system with description of length 256 characters
2.
3.
Actual results:
Operating system created with no errors
Expected results:
Until last build, we allowed os description length upto a maximum of 255 characters only, now its broken.
Additional info:
Comment 4Oleksandr Shtaier
2016-04-21 08:50:54 UTC
Raising the severity as operating system is unique entity in a way that Title of such entity is formed using not only name, but description too. We have similar increase of description length across other entities, but for them impact is minimal and do not transform table in a bad shape to make user experience worse.
Saying that we have a valid issue, no matter what reason get us there, so corresponding database field has to have sensible limit and we have to force it.
Comment 5Daniel Lobato Garcia
2016-04-22 14:11:33 UTC
Oleksander,
What should suffice here is to set sat-6.2.z flag to '?'
But as you can see it gets changed to '+' shortly
Comment 16Satellite 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