Bug 1641223
Summary: | Can't create a new session in foreman: integer out of range | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Alexey Masolov <amasolov> |
Component: | Users & Roles | Assignee: | Suraj Patil <supatil> |
Status: | CLOSED ERRATA | QA Contact: | Radovan Drazny <rdrazny> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.4 | CC: | akapse, amasolov, andrew.schofield, baitken, bbuckingham, cmarinea, dhlavacd, inecas, jko, mhulan, oezr, oprazak, pdudley, satellite6-bugs, sthirugn, wpinheir |
Target Milestone: | 6.7.0 | Keywords: | FieldEngineering, PrioBumpField, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman-1.24.1.5-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-14 13:23:25 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
Alexey Masolov
2018-10-20 03:56:02 UTC
Created redmine issue http://projects.theforeman.org/issues/26009 from this bug *** Bug 1758292 has been marked as a duplicate of this bug. *** Linking an issue, that contains an easyfix. Verified on Sat 6.7 Snap 15. Logged out from the WebUI, run 'foreman-rake db:sessions:clear' $ sudo -u foreman psql foreman=> select * from sessions_id_seq; sequence_name | last_value | start_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called -----------------+------------+-------------+--------------+---------------------+-----------+-------------+---------+-----------+----------- sessions_id_seq | 269 | 1 | 1 | 9223372036854775807 | 1 | 1 | 29 | t | t (1 row) The max value has been set to the PG bigint value. foreman=> alter sequence sessions_id_seq restart with 9223372036854775807; ALTER SEQUENCE foreman=> select * from sessions_id_seq; sequence_name | last_value | start_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called -----------------+---------------------+-------------+--------------+---------------------+-----------+-------------+---------+-----------+----------- sessions_id_seq | 9223372036854775807 | 1 | 1 | 9223372036854775807 | 1 | 1 | 0 | t | f (1 row) Logged back into the WebUI, did some clicking around. foreman=> select * from sessions_id_seq; sequence_name | last_value | start_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called -----------------+------------+-------------+--------------+---------------------+-----------+-------------+---------+-----------+----------- sessions_id_seq | 5 | 1 | 1 | 9223372036854775807 | 1 | 1 | 29 | t | t (1 row) The value correctly rolled over the bigint limit, and started the sequence from 1 again. 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 |