-
Bug
-
Resolution: Unresolved
-
Blocker
-
6.17.6.2
-
2
-
False
-
Artemis Sprint 162, Artemis Sprint 163
-
sat-artemis
-
None
-
None
-
None
-
No Coverage
Similar to what was reported in https://issues.redhat.com/browse/SAT-34624 , we now get to see the same happeing for katello_rpms_id_seq and katello_rpms.id itself.
The environment ran into this issue, has a Sat 6.17.6 with 24 orgs and daily sync plans active.
Error:
ActiveRecord::StatementInvalid: PG::SequenceGeneratorLimitExceeded: ERROR: nextval: reached maximum value of sequence "katello_rpms_id_seq" (2147483647)
Details from DB:
foreman=# select * from pg_sequences where sequencename='katello_rpms_id_seq'; schemaname | sequencename | sequenceowner | data_type | start_value | min_value | max_value | increment_by | cycle | cache_size | last_value ------------+---------------------+---------------+-----------+-------------+-----------+------------+--------------+-------+------------+------------ public | katello_rpms_id_seq | foreman | integer | 1 | 1 | 2147483647 | 1 | f | 1 | 2147483647 (1 row)
We had foreseen this during the investigation of the aforementioned Jira as well.
Requesting to :
- Set the datatype of katello_rpms_id_seq to bigint
- Set the type of katello_rpms.id to bigint as well.