Bug 1793701
Summary: | Content View publishing fails after katello_repository_rpms "id" column hits max integer size | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Dylan Gross <dgross> | ||||
Component: | Content Management | Assignee: | Justin Sherrill <jsherril> | ||||
Status: | CLOSED ERRATA | QA Contact: | Lai <ltran> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.6.0 | CC: | jsherril, zhunting | ||||
Target Milestone: | 6.7.0 | Keywords: | Triaged | ||||
Target Release: | Unused | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | tfm-rubygem-katello-3.14.0.10-1 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-04-14 13:28:34 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
Dylan Gross
2020-01-21 21:17:08 UTC
Created redmine issue https://projects.theforeman.org/issues/28831 from this bug Created attachment 1654409 [details]
database migration file
To apply patch: Drop the attached file into the /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.12.0.29/db/migrate/ directory, so that it exists as: /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.12.0.29/db/migrate/20200121213430_katello_repository_rpms_id_big_int.rb Run: foreman-rake db:migrate systemctl restart httpd dynflowd Upstream bug assigned to jsherril Upstream bug assigned to jsherril Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28831 has been resolved. Steps to retest: 1. Check postgres database table for BIGINT for ID column. Expected result: id -> bigint Actual result: foreman=# \d katello_repository_rpms Table "public.katello_repository_rpms" Column | Type | Modifiers ---------------+-----------------------------+----------------------------------------------------------- ----------- id | bigint | not null default nextval('katello_repository_rpms_id_seq': :regclass) rpm_id | integer | not null repository_id | integer | created_at | timestamp without time zone | updated_at | timestamp without time zone | Indexes: Second way of verifying: 1. Create a custom repo 2. Sync repo 3. Create cv and add custom repo from step 1 4. Publish cv 5. Log into postgres database 6. Update id to something above the 2,147,483,647 max. i.e. foreman=# update katello_repository_rpms set id=3147478933 where id in (Select max(id) from katello_repository_rpms); Expected result: UPDATE 1 Actual result: UPDATE 1 Note: For the second way of verifying, if you update above the 2147483647 max, it'll give "ERROR: integer out of range" IF THE ID DATATYPE was still in "integer". Switching to "bigint" has a higher max value so it should not give the error message. In this case, it did not give the error message. Tested on 6.7.0_011. Marking issue as verified. 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-2020:1454 |