haha - it must have heard me, it just finished and carried on to the next steps, go figure! So 176GB of pulp data takes roughly 6 hours ;-) (suppose it'll be different based on hardware etc!)
Dylan On Friday, July 1, 2016 at 4:03:29 PM UTC+12, Dylan Baars wrote: > > Hi Jason, > > how long did it take in the end? I am upgrading our production katello > instance from 2.4.4 to 3.0, and the pulp_migrate step has taken 6 hours so > far - I see no errors in the logs and pulp-manage-db seems to be running, > taking CPU and memory time up. Our production system has a much larger pulp > repository than the test instance I've done this on, but is there any > advice on how long this step should take? (more a question for the Katello > devs I guess!) It is 4pm here now, but the last logs in /var/log/messages > from pulp are below (from 10:15am) > > Jul 1 10:15:49 wellkatello.niwa.local pulp: py.warnings:WARNING: > (21830-39488) multi=True) > Jul 1 10:15:49 wellkatello.niwa.local pulp: py.warnings:WARNING: > (21830-39488) > Jul 1 10:15:49 wellkatello.niwa.local pulp: pulp.server.db.manage:INFO: > Migration to pulp_rpm.plugins.migrations version 27 complete. > Jul 1 10:15:49 wellkatello.niwa.local pulp: pulp.server.db.manage:INFO: > Applying pulp_rpm.plugins.migrations version 28 > > /var/lib/pulp is 176G vs the 42GB on the test instance > > Thanks, > Dylan > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
