Bug 2278566
Summary: | Content view publish failing with katello_repository_rpms_id_seq reached maximum value error | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Ashfaqur Rahaman <arahaman> |
Component: | Content Views | Assignee: | Ian Ballou <iballou> |
Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.13.6 | CC: | iballou, jpasqual, juqiao, mkushwah, sajha, satellite6-bugs, sbible, zhunting |
Target Milestone: | stream | Keywords: | MigratedToJIRA, WorkAround |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-06 17:36:18 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: |
Description
Ashfaqur Rahaman
2024-05-02 04:35:25 UTC
Created redmine issue https://projects.theforeman.org/issues/37403 from this bug Upstream bug assigned to iballou Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37403 has been resolved. Version-Release number of selected component (if applicable): 6.16 - Stream 60 How reproducible: Always Steps to Reproduce: 1. Login to the command line of Satellite, and access the foreman postgres shell (sudo -u postgres psql foreman) 2. Run the following command: select * from pg_sequences where sequencename='katello_repository_rpms_id_seq'; Actual results: The data_type of this field (katello_repository_rpms_id_seq) is bigint, and isn't integer. Expected results: The data_type of this field (katello_repository_rpms_id_seq) is bigint, and isn't integer. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |