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.

Bug 1314519

Summary:	Specify string column limits
Product:	Red Hat Satellite	Reporter:	Partha Aji <paji>
Component:	Content Management	Assignee:	David Davis <daviddavis>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	bbuckingham, cwelton, jcallaha, kbidarka, paji
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14025
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 09:25:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Partha Aji 2016-03-03 20:00:30 UTC

In Rails 4.2 the default limit for PostgreSQL and SQLite adapters
changes to unlimited from 255 characters.  MySQL remains at 255 chars.
Existing migrations should be changed to specify the length, e.g.

  t.column :name, :string, :null => false, :limit => 255

This will ensure that the schema generated on a new installation exactly
matches the schema from an old installation, so there won't be varying
versions of the schema in the wild.

Comment 1 Partha Aji 2016-03-03 20:00:32 UTC

Created from redmine issue http://projects.theforeman.org/issues/14025

Comment 2 Partha Aji 2016-03-03 20:00:35 UTC

Upstream bug assigned to daviddavis

Comment 4 Bryan Kearney 2016-03-03 21:11:30 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/14025 has been closed
-------------
David Davis
Applied in changeset commit:katello|924700524dd6990d447030dcfb92caed0c28c3f2.

Comment 6 Kedar Bidarkar 2016-05-25 15:58:07 UTC

Please provide verification steps to test this.

Comment 7 David Davis 2016-05-28 21:39:48 UTC

Try entering a value longer than 255 chars for one of these fields:

https://github.com/Katello/katello/pull/5837/files

It must be a new install. A few example fields include activation key name, content view name, lifecycle environment name, etc

Comment 8 jcallaha 2016-06-16 14:13:51 UTC

Verified in Satellite 6.2 beta Snap 15.2

Forms accepting string input are correctly performing string length validation.

Comment 10 errata-xmlrpc 2016-07-27 09:25:25 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