mirror-registry upgrade to version 2.x never finish

[indor79]

I have a problem trying to upgrade mirror-registry from version 1.x to 2.x

It is stuck at the task

TASK [mirror_appliance : Take a pg_dump of the data from running quay-postgres container]

The ansible container is running and it looks like it is doing something but it never finish.

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
3841780 openshi+  20   0 2376540   2.0g  11136 R  98.7   8.6 117:26.16 /usr/bin/python3 /home/openshift/.ansible/tmp/ansible-tmp-1741685852.8751273-364-31487022408172/AnsiballZ_command.py

I am starting to think it's a memory issue. Looking at the code it seems it is trying to load everything in memory? Could that be the issue here? I do not have any proof but I do see the memory usage of the ansible container going up and down a lot.

mirror-registry/ansible-runner/context/app/project/roles/mirror_appliance/tasks/migrate.yaml

Lines 35 to 40 in 862946d

	- name: Take a pg_dump of the data from running quay-postgres container
	command: >
	podman exec -it quay-postgres
	pg_dump --data-only --column-inserts --no-owner --no-privileges --disable-triggers
	-U user -d quay
	register: pg_dump_output

I am trying to upgrade to mirror-registry version 2.0.5

[indor79]

I guess the number of records affect the needed amount of memory? Maybe it would be better to transfer the data using a file instead of doing it in memory?

$ podman exec quay-postgres sh -c "pg_dump --data-only --column-inserts --no-owner --no-privileges --disable-triggers -U user -d quay | wc -c"
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump:   apprtag
pg_dump: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a --data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump:   tag
pg_dump: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a --data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump:   repomirrorrule
pg_dump: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a --data-only dump to avoid this problem.
10017260650