[Pulp-list] Database migration from 3.3 to 3.7

Mon Dec 7 16:03:35 UTC 2020

We are running rhel7.6. The installer was stuck on database migration for almost 2 hours. It eventually went through. Not sure why it took such a long time. I was wondering if I should send a break. I saved pg_stat_activity output from postgresql. My question is if I can tell the progress of the database migration from any logs or postgresql so I know if the process is really got stuck or just very slow?

From: bmbouter at redhat.com At: 12/05/20 10:46:19To:  Bin Li (BLOOMBERG/ 120 PARK ) 
Cc:  pulp-list at redhat.com
Subject: Re: [Pulp-list] Database migration from 3.3 to 3.7

Maybe it's selinux labeling related. What step is it stuck on in the installer's output? What OS are you using?

On Sat, Dec 5, 2020 at 9:48 AM Bin Li (BLOOMBERG/ 120 PARK) <bli111 at bloomberg.net> wrote:

We are upgrading pulp from 3.3 to 3.7.  Ansible stuck on database migration for more that 50 mins. We have 1.5T of artifact in file system. The database size is about 25G.  Is this normal? Is there a way we can check the progress log? _______________________________________________
Pulp-list mailing list
Pulp-list at redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20201207/c30cc6c1/attachment.htm>