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.
DescriptionFotios Tsiadimos
2016-03-24 18:39:51 UTC
Description of problem:
Satellite 6.1
The patch removes the limit varchar(4096) which will be released in 6.2. Can we have also a patch for the version 6.1.
foreman=# \d ptables
Table "public.ptables"
Column | Type | Modifiers
------------+-----------------------------+------------------------------------------------------
id | integer | not null default nextval('ptables_id_seq'::regclass)
name | character varying(255) | not null
layout | character varying(4096) | not null <=== it has a MAX varchar() limit on the table
created_at | timestamp without time zone | not null
updated_at | timestamp without time zone | not null
os_family | character varying(255) |
Indexes:
Always, it is documented in the named foreman issues:
http://projects.theforeman.org/issues/12119http://projects.theforeman.org/issues/3008
There is also a fix that has been committed for foreman 1.8:
https://github.com/theforeman/foreman/pull/2113/files
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:1938
Description of problem: Satellite 6.1 The patch removes the limit varchar(4096) which will be released in 6.2. Can we have also a patch for the version 6.1. foreman=# \d ptables Table "public.ptables" Column | Type | Modifiers ------------+-----------------------------+------------------------------------------------------ id | integer | not null default nextval('ptables_id_seq'::regclass) name | character varying(255) | not null layout | character varying(4096) | not null <=== it has a MAX varchar() limit on the table created_at | timestamp without time zone | not null updated_at | timestamp without time zone | not null os_family | character varying(255) | Indexes: Always, it is documented in the named foreman issues: http://projects.theforeman.org/issues/12119 http://projects.theforeman.org/issues/3008 There is also a fix that has been committed for foreman 1.8: https://github.com/theforeman/foreman/pull/2113/files