Installation & Migration to Podman 2024.8 => 2024.12 - FATAL: Ident authentication failed for user "pythia_susemanager"

[greinickfa]

Problem description

running "mgradm migrate podman uyuni.filmakademie.de" leads to an error:

2:31PM ??? Starting Postgresql...
2:31PM ??? 2025-01-13 14:31:20.727 CET [43]LOG: redirecting log output to logging collector process
2025-01-13 14:31:20.727 CET [43]HINT: Future log output will appear in directory "log".
2:31PM ??? Reindexing database. This may take a while, please do not cancel it!
2:33PM ??? REINDEX
2:33PM ??? Schema update...
2:33PM ??? report_db_host = localhost
2:33PM ??? psql: error: connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "pythia_susemanager"

Steps to reproduce

Follow the doc from https://www.uyuni-project.org/uyuni-docs/en/uyuni/installation-and-upgrade/container-deployment/uyuni/migrate-uyuni-to-a-container.html

Uyuni version

Migrating from 2024.8 => 2024.12

Uyuni proxy version (if used)

No response

Useful logs

ostgresql...
2:31PM ??? 2025-01-13 14:31:20.727 CET   [43]LOG:  redirecting log output to logging collector process
2025-01-13 14:31:20.727 CET   [43]HINT:  Future log output will appear in directory "log".
2:31PM ??? Reindexing database. This may take a while, please do not cancel it!
2:33PM ??? REINDEX
2:33PM ??? Schema update...
2:33PM ??? report_db_host = localhost
2:33PM ??? psql: error: connection to server at "localhost" (::1), port 5432 failed: FATAL:  Ident authentication failed for user "pythia_susemanager"
2:33PM ??? Schema upgrade: [susemanager-schema-4.4.2-220400.1.4.uyuni2] -> [susemanager-schema-5.1.2-241000.1.1.uyuni5]
Searching for upgrade path to: [susemanager-schema-5.1.2-241000]
Searching for upgrade path to: [susemanager-schema-5.1.2]
Searching for start path:  [susemanager-schema-4.4.2-220400]
Searching for start path:  [susemanager-schema-4.4.2]
The path: [susemanager-schema-4.4.2] -> [susemanager-schema-4.4.3] -> [susemanager-schema-4.4.4] -> [susemanager-schema-4.4.5] -> [susemanager-schema-4.4.6] -> [susemanager-schema-4.4.7] -> [susemanager-schema-4.4.8] -> [susemanager-schema-4.4.9] -> [susemanager-schema-4.4.10] -> [susemanager-schema-5.0.0] -> [susemanager-schema-5.0.1] -> [susemanager-schema-5.0.2] -> [susemanager-schema-5.0.3] -> [susemanager-schema-5.0.4] -> [susemanager-schema-5.0.5] -> [susemanager-schema-5.0.6] -> [susemanager-schema-5.0.7] -> [susemanager-schema-5.0.8] -> [susemanager-schema-5.0.9] -> [susemanager-schema-5.0.10] -> [susemanager-schema-5.0.11] -> [susemanager-schema-5.1.0] -> [susemanager-schema-5.1.1] -> [susemanager-schema-5.1.2]
2:33PM ??? Planning to run schema upgrade with dir '/var/log/spacewalk/schema-upgrade/schema-from-20250113-133311'
2:33PM ??? Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20250113-133311-to-susemanager-schema-5.1.2.log].
2:33PM ??? (1/80) apply upgrade [schema-from-20250113-133311/00_0000-upgrade-start.sql]        
2:33PM ??? (2/80) apply upgrade [susemanager-schema-4.4.2-to-susemanager-schema-4.4.3/001-remove-kickstart-below-rhel6.sql.postgresql]        
2:33PM ??? (3/80) apply upgrade [susemanager-schema-4.4.2-to-susemanager-schema-4.4.3/001-varchar-length-suseRecurringAction.sql.postgresql]        
2:33PM ??? (4/80) apply upgrade [susemanager-schema-4.4.2-to-susemanager-schema-4.4.3/002-systems-overview.sql.postgresql]        
2:33PM ??? (5/80) apply upgrade [susemanager-schema-4.4.2-to-susemanager-schema-4.4.3/100-rename_monitoring_entitlement.sql.postgresql]        
2:33PM ??? (6/80) apply upgrade [susemanager-schema-4.4.2-to-susemanager-schema-4.4.3/900-add-pane-subwarn-rhnInfoPane.sql.postgresql]        
2:33PM ??? (7/80) apply upgrade [susemanager-schema-4.4.3-to-susemanager-schema-4.4.4/000-uyuni-fix-ol9-repos.sql.postgresql]        
2:33PM ??? (8/80) apply upgrade [susemanager-schema-4.4.3-to-susemanager-schema-4.4.4/100-suseContentFilter-null-values.sql.postgresql]        
2:33PM ??? (9/80) apply upgrade [susemanager-schema-4.4.3-to-susemanager-schema-4.4.4/400-ptf-package-visibility.sql.postgresql]        
2:33PM ??? (10/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/001-rhnCPU-enhancement.sql.postgresql]        
2:33PM ??? (11/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/002-deregister-foreign-systems.sql.postgresql]        
2:33PM ??? (12/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/003-update-sccregcache-trigger.sql.postgresql]        
2:33PM ??? (13/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/004-system-profile-refresh-task.sql.postgresql]        
2:33PM ??? (14/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/010-add-pkey-taskQueue.sql.postgresql]        
2:33PM ??? (15/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/011-update-queue_image.sql.postgresql]        
2:33PM ??? (16/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/012-update-queue_server.sql.postgresql]        
2:33PM ??? (17/80) apply upgrade [susemanager-schema-4.4.4-to-susemanager-schema-4.4.5/020-taskorun-paths-removal.sql.postgresql]        
2:33PM ??? (18/80) apply upgrade [susemanager-schema-4.4.5-to-susemanager-schema-4.4.6/000-change-leap-gpgkeyurl.sql.postgresql]        
2:33PM ??? (19/80) apply upgrade [susemanager-schema-4.4.5-to-susemanager-schema-4.4.6/001-rhnChannelComps-revert_drop_uidx.sql.postgresql]        
2:33PM ??? (20/80) apply upgrade [susemanager-schema-4.4.5-to-susemanager-schema-4.4.6/002-update-function-create_new_org.sql.postgresql]        
2:33PM ??? (21/80) apply upgrade [susemanager-schema-4.4.5-to-susemanager-schema-4.4.6/100-rename_monitoring_entitlement.sql.postgresql]        
2:33PM ??? (22/80) apply upgrade [susemanager-schema-4.4.6-to-susemanager-schema-4.4.7/001-add-rhui-credential-type.sql.postgresql]        
2:33PM ??? (23/80) apply upgrade [susemanager-schema-4.4.6-to-susemanager-schema-4.4.7/100-update-recurring-action.sql.postgresql]        
2:33PM ??? (24/80) apply upgrade [susemanager-schema-4.4.6-to-susemanager-schema-4.4.7/200-payg-add-computation-tables.sql.postgresql]        
2:33PM ??? (25/80) apply upgrade [susemanager-schema-4.4.6-to-susemanager-schema-4.4.7/201-payg-taskomatic.sql.postgresql]        
2:33PM ??? (26/80) apply upgrade [susemanager-schema-4.4.6-to-susemanager-schema-4.4.7/202-payg-products.sql.postgresql]        
2:33PM ??? (27/80) apply upgrade [susemanager-schema-4.4.8-to-susemanager-schema-4.4.9/001-improve-ubuntu-errata-processing.sql.postgresql]        
2:33PM ??? (28/80) apply upgrade [susemanager-schema-4.4.8-to-susemanager-schema-4.4.9/002-add-serverneededcache-index.sql.postgresql]        
2:33PM ??? (29/80) apply upgrade [susemanager-schema-4.4.8-to-susemanager-schema-4.4.9/100-gpg-amazonlinux2023.sql.postgresql]        
2:33PM ??? (30/80) apply upgrade [susemanager-schema-4.4.8-to-susemanager-schema-4.4.9/120-armhf.sql.postgresql]        
2:33PM ??? (31/80) apply upgrade [susemanager-schema-4.4.8-to-susemanager-schema-4.4.9/200-rename-ssh-push-task.sql.postgresql]        
2:33PM ??? (32/80) apply upgrade [susemanager-schema-4.4.8-to-susemanager-schema-4.4.9/204-revert-changelogdata-index.sql.postgresql]        
2:33PM ??? (33/80) apply upgrade [susemanager-schema-4.4.8-to-susemanager-schema-4.4.9/300-add-qrtz-missing-table.sql.postgresql]        
2:33PM ??? (34/80) apply upgrade [susemanager-schema-4.4.9-to-susemanager-schema-4.4.10/100-update-credentials.sql.postgresql]        
2:33PM ??? (35/80) apply upgrade [susemanager-schema-4.4.9-to-susemanager-schema-4.4.10/200-reboot-required-any-distro.sql.postgresql]        
2:33PM ??? (36/80) apply upgrade [susemanager-schema-4.4.9-to-susemanager-schema-4.4.10/201-replace-update-system-overview.sql.postgresql]        
2:33PM ??? (37/80) apply upgrade [susemanager-schema-4.4.9-to-susemanager-schema-4.4.10/203-enable-pillar-refresh.sql.postgresql]        
2:33PM ??? (38/80) apply upgrade [susemanager-schema-5.0.3-to-susemanager-schema-5.0.4/200-change-sys-profile-refresh-schedule.sql.postgresql]        
2:33PM ??? (39/80) apply upgrade [susemanager-schema-5.0.4-to-susemanager-schema-5.0.5/002-store-vulnerable-packages.sql.postgresql]        
2:33PM ??? (40/80) apply upgrade [susemanager-schema-5.0.4-to-susemanager-schema-5.0.5/100-add-internal-state-update-salt.sql.postgresql]        
2:33PM ??? (41/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/001-oval-add-tables.sql.postgresql]        
2:33PM ??? (42/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/010-add-cocoattestation-tables.sql.postgresql]        
2:33PM ??? (43/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/010-clean-bootstrap-activation-keys.sql.postgresql]        
2:33PM ??? (44/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/011-suseServerCoCoAttestationReport-trigger.sql.postgresql]        
2:33PM ??? (45/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/012-add-coco_attestation-action-type.sql.postgresql]        
2:33PM ??? (46/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/013-suseCoCoAttestationResult-trigger.sql.postgresql]        
2:33PM ??? (47/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/100-peripheral_server_entitlement.sql.postgresql]        
2:33PM ??? (48/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/101-create_new_org.sql.postgresql]        
2:33PM ??? (49/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/200-create-rhnchannelsyncflag.sql.postgresql]        
2:33PM ??? (50/80) apply upgrade [susemanager-schema-5.0.5-to-susemanager-schema-5.0.6/200-enable-all-systems-sync-all.sql.postgresql]        
2:33PM ??? (51/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/001-add-package-keys.sql.postgresql]        
2:33PM ??? (52/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/001-coco-changes-for-ui.sql.postgresql]        
2:33PM ??? (53/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/002-coco-add-process-output.sql.postgresql]        
2:33PM ??? (54/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/100-update-proxy-info.sql.postgresql]        
2:33PM ??? (55/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/200-enable-pillar-refresh.sql.postgresql]        
2:33PM ??? (56/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/500-suseAppstream-create.sql.postgresql]        
2:33PM ??? (57/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/501-suseAppstreamApi-create.sql.postgresql]        
2:33PM ??? (58/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/502-suseAppstreamPackage-create.sql.postgresql]        
2:33PM ??? (59/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/503-add-table-server-appstream.sql.postgresql]        
2:33PM ??? (60/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/520-change-channel-newest-package-table-view.sql.postgresql]        
2:33PM ??? (61/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/521-add-server-appstreams-views.sql.postgresql]        
2:33PM ??? (62/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/522-rhn_channel.pkb.sql.postgresql]        
2:33PM ??? (63/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/523-rhn_server.pkb.sql.postgresql]        
2:33PM ??? (64/80) apply upgrade [susemanager-schema-5.0.6-to-susemanager-schema-5.0.7/530-add-appstreams_change-details-and-action-type.sql.postgresql]        
2:33PM ??? (65/80) apply upgrade [susemanager-schema-5.0.7-to-susemanager-schema-5.0.8/001-fix-channel-sync-flag-primary-key.sql.postgresql]        
2:33PM ??? (66/80) apply upgrade [susemanager-schema-5.0.7-to-susemanager-schema-5.0.8/001-optimize-appstreams-hidden-packages-views.sql.postgresql]        
2:33PM ??? (67/80) apply upgrade [susemanager-schema-5.0.10-to-susemanager-schema-5.0.11/001-change-cobbler-sync-schedule.sql.postgresql]        
2:33PM ??? (68/80) apply upgrade [susemanager-schema-5.0.10-to-susemanager-schema-5.0.11/002-remove-minonactionchaincleanup.sql.postgresql]        
2:33PM ??? (69/80) apply upgrade [susemanager-schema-5.0.10-to-susemanager-schema-5.0.11/100-split-updtodate-state.sql.postgresql]        
2:33PM ??? (70/80) apply upgrade [susemanager-schema-5.0.10-to-susemanager-schema-5.0.11/100-suseRegTokenAppStreams-create.sql.postgresql]        
2:33PM ??? (71/80) apply upgrade [susemanager-schema-5.0.10-to-susemanager-schema-5.0.11/200-fix-appstreams-related-views.sql.postgresql]        
2:33PM ??? (72/80) apply upgrade [susemanager-schema-5.0.10-to-susemanager-schema-5.0.11/300-replace-susePackageExcludingPartOfPtf-view.sql.postgresql]        
2:33PM ??? (73/80) apply upgrade [susemanager-schema-5.1.0-to-susemanager-schema-5.1.1/001-oval-taskomatic.sql.postgresql]        
2:33PM ??? (74/80) apply upgrade [susemanager-schema-5.1.0-to-susemanager-schema-5.1.1/002-errata-view-optimization.sql.postgresql]        
2:33PM ??? (75/80) apply upgrade [susemanager-schema-5.1.0-to-susemanager-schema-5.1.1/010-foreign-groups.sql.postgresql]        
2:33PM ??? (76/80) apply upgrade [susemanager-schema-5.1.1-to-susemanager-schema-5.1.2/000-convert-reportdb-users-to-lowercase.sql.postgresql]        
2:33PM ??? (77/80) apply upgrade [susemanager-schema-5.1.1-to-susemanager-schema-5.1.2/001-drop-extensions.sql.postgresql]        
2:33PM ??? (78/80) apply upgrade [susemanager-schema-5.1.1-to-susemanager-schema-5.1.2/002-rhnActionApplyStates.sql.postgresql]        
2:33PM ??? (79/80) apply upgrade [susemanager-schema-5.1.1-to-susemanager-schema-5.1.2/003-appstream-hidden-packages-view.sql.postgresql]        
2:33PM ??? (80/80) apply upgrade [schema-from-20250113-133311/99_9999-upgrade-end.sql]        
2:33PM ???
2:33PM ??? The database schema was upgraded to version [susemanager-schema-5.1.2-241000.1.1.uyuni5].
2:33PM ??? psql: error: connection to server at "localhost" (::1), port 5432 failed: FATAL:  Ident authentication failed for user "pythia_susemanager"
2:33PM ??? Connect to database was not successful.
2:33PM ??? Report Database schema upgrade failed. Please check the logs.
Error: cannot run PostgreSQL finalize script: failed to run uyuni-finalize-pgsql container: exit status 1
uyuni:~ #

Additional information

I saw and read some other issue reports e.g. #9268 but got lost and very confused ... e.g. do I have to restart the source (old) uyuni postgres server or not?

If I have to change the pg_hba.conf what are the generic settings, what are my environment settings?

May I restart the migration or do I really have to clean all new repo date (in my case 1.2 TB) ? Or can I proceed (sort of retry/rerun) with the current state?

mgradm --version
mgradm version 5.1.4 (Master 3640be2)

The old server is running postgres (PostgreSQL) 14.13

Thanks and regards for suggestions and help!

[cseres3]

I have the same problem. Trying to migrate data from 2024.08 (Leap 15.5) to 2024.12 (Leap Micro 5.5).

mgradm migrate podman old.uyuni-server.fi --prepare
succeeds, but without --prepare it gives

9:49PM ??? The database schema was upgraded to version [susemanager-schema-5.1.2-241000.1.1.uyuni5]. 9:49PM ??? psql: error: connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "pythia_susemanager" 9:49PM ??? Connect to database was not successful. 9:49PM ??? Report Database schema upgrade failed. Please check the logs. Error: cannot run PostgreSQL finalize script: failed to run uyuni-finalize-pgsql container: exit status 1

I would like to know the recommended way to get past this. I have tried the suggestions in #9268 about /var/lib/pgsql/data/pg_hba.conf, but the changes just lead to different error messages in earlier stages. After failed try I did

cd /var/lib/containers/storage/volumes/var-pgsql/_data rm -rf data-pg14/ delete_old_cluster.sh initlog .bash_profile

which got me past the error ??? mv: cannot move '/var/lib/pgsql/data' to '/var/lib/pgsql/data-pg14/data': File exists

I also tried to execute smdba db-start when REINDEX was shown, as suggested in the same issue, but that did not change anything. I am not familiar with PostrgeSQL so I might have just skipped something.

What would be a simple test to rerun the migration with a minimal and known good pga_hb.conf and try to fix the problem? I have a snapshot, but it takes several days if I have to start from the beginning as there are several terabytes of data on a slow disk so if possible, I would just like to rerun the final migration with a working config.

Additional information
/var/lib/pgsql/data/pg_hba.conf on the source:
local reportdb postgres peer local uyuni uyuni scram-sha-256 host uyuni uyuni 127.0.0.1/8 scram-sha-256 host uyuni uyuni ::1/128 scram-sha-256 local all all peer host all all 127.0.0.1/32 ident host all all ::1/128 ident local replication all peer host replication all 127.0.0.1/32 ident host replication all ::1/128 ident local replication postgres peer local reportdb all scram-sha-256 host reportdb all 127.0.0.1/32 scram-sha-256 host reportdb all ::1/128 scram-sha-256 host reportdb all 0.0.0.0/0 scram-sha-256 host reportdb all ::/0 scram-sha-256
/var/lib/containers/storage/volumes/var-pgsql/_data/data/pg_hba.conf on the target:
local reportdb postgres peer local uyuni uyuni scram-sha-256 host uyuni uyuni 127.0.0.1/8 scram-sha-256 host uyuni uyuni ::1/128 scram-sha-256 local all all peer host all all 127.0.0.1/32 ident host all all ::1/128 ident local replication all peer host replication all 127.0.0.1/32 ident host replication all ::1/128 ident local replication postgres peer local reportdb all scram-sha-256 host reportdb all 127.0.0.1/32 scram-sha-256 host reportdb all ::1/128 scram-sha-256 host reportdb all 0.0.0.0/0 scram-sha-256 host reportdb all ::/0 scram-sha-256

Hosts have both IPv4 and IPv6 addresses.