-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.13.0
-
None
-
False
-
None
-
False
-
-
Description:
This is an issue found in Quay 3.13, when deploy Quay with Quay Operator using managed Clair and Clair Postgres Components, the Clair Postgres POD was crashed, pls review this issue.
Quay: quay-operator-bundle-container-v3.13.0-34
oc get pod NAME READY STATUS RESTARTS AGE quay-operator.v3.13.0-5554c67dd7-4br7f 1/1 Running 0 56m quayregistry-clair-app-54dd77dc57-4j9f7 1/1 Running 2 (50m ago) 50m quayregistry-clair-app-54dd77dc57-k77rd 1/1 Running 0 39m quayregistry-clair-postgres-6d8956ff7d-g8xrp 0/1 CrashLoopBackOff 14 (2m21s ago) 50m quayregistry-clair-postgres-6d8956ff7d-gkmtc 0/1 CrashLoopBackOff 12 (81s ago) 50m quayregistry-clair-postgres-old-f8f96c8f7-gpsdj 1/1 Running 0 7m42s quayregistry-clair-postgres-upgrade-9xv86 1/1 Running 4 (114s ago) 7m42s quayregistry-quay-app-75bf477c94-49dlm 1/1 Running 0 50m quayregistry-quay-app-75bf477c94-czwjn 1/1 Running 2 (50m ago) 51m quayregistry-quay-app-upgrade-g5l4c 0/1 Completed 2 52m quayregistry-quay-database-69c66d9d55-7j9fm 1/1 Running 0 51m quayregistry-quay-mirror-77cff4ffc9-fwd7x 1/1 Running 0 51m quayregistry-quay-mirror-77cff4ffc9-ptx69 1/1 Running 0 51m quayregistry-quay-redis-64c49b576f-rbmnv 1/1 Running 0 51m oc logs quayregistry-clair-postgres-6d8956ff7d-g8xrp pg_ctl: another server might be running; trying to start server anyway waiting for server to start....2024-10-09 03:30:26.156 GMT [24] LOG: redirecting log output to logging collector process 2024-10-09 03:30:26.156 GMT [24] HINT: Future log output will appear in directory "log". ..... done server started /var/run/postgresql:5432 - rejecting connections
Clair Postgres upgrade POD:
oc logs quayregistry-clair-postgres-6d8956ff7d-g8xrp pg_ctl: another server might be running; trying to start server anyway waiting for server to start....2024-10-09 03:30:26.156 GMT [24] LOG: redirecting log output to logging collector process 2024-10-09 03:30:26.156 GMT [24] HINT: Future log output will appear in directory "log". ..... done server started /var/run/postgresql:5432 - rejecting connections oc logs quayregistry-clair-postgres-upgrade-9xv86 The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale "en_US.utf8". The default database encoding has accordingly been set to "UTF8". The default text search configuration will be set to "english". Data page checksums are disabled. fixing permissions on existing directory /var/lib/pgsql/data/userdata ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... Etc/UTC creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok syncing data to disk ... ok initdb: warning: enabling "trust" authentication for local connections initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. Success. You can now start the database server using: pg_ctl -D /var/lib/pgsql/data/userdata -l logfile start waiting for server to start....2024-10-09 03:31:47.625 GMT [36] LOG: redirecting log output to logging collector process 2024-10-09 03:31:47.625 GMT [36] HINT: Future log output will appear in directory "log". done server started /var/run/postgresql:5432 - accepting connections SET SET SET ALTER ROLE You are now connected to database "template1" as user "postgres". SET SET SET SET SET set_config ------------ (1 row) SET SET SET SET ALTER SCHEMA REVOKE GRANT You are now connected to database "postgres" as user "postgres". SET SET SET SET SET set_config ------------ (1 row) SET SET SET SET ALTER SCHEMA CREATE EXTENSION COMMENT CREATE TYPE ALTER TYPE CREATE TYPE ALTER TYPE SET SET CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE MATERIALIZED VIEW ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE VIEW ALTER TABLE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE CREATE TABLE ALTER TABLE CREATE SEQUENCE ALTER TABLE ALTER SEQUENCE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE COPY 2 COPY 0 COPY 160996 COPY 566 COPY 0 COPY 0 COPY 0 COPY 0 COPY 7 COPY 12 COPY 0 COPY 0 COPY 0 COPY 529 COPY 0 COPY 3 COPY 529 COPY 945 COPY 0 COPY 529 COPY 1 COPY 0 COPY 0 COPY 0 COPY 20 COPY 0 COPY 160996 COPY 10914635 COPY 552 COPY 495 WARNING: terminating connection due to immediate shutdown command server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. invalid socket connection to server was lost pg_dumpall: error: pg_dump failed on database "postgres", exiting postgres migration command failed, cleaning up...
- links to
- mentioned on
