I'll toss up some supplemental info, as I had the same experience, I started the upgrade on a Friday afternoon, and came back in on the following Tuesday to find it still sitting at the Pulp upgrade step. I performed an strace on the corresponding rake process, and found it was performing a slew of stat, link, and unlink operations for RPM file references in /var/lib/pulp. On a hunch that it was performing this process on every single directory that correlates with a Content View, I used the cvmanager utility from GitHub ( https://github.com/evgeni/katello-cvmanager/blob/master/ ) to clean up all Content Views beyond the three most recent versions for all of our Products, and my ensuing attempt to upgrade took a mere two to three hours. Case and point, if you're like me and have a lot of Content Views, then this is likely negatively impacting the upgrade process and it's suggested to clean them up prior to completing it. I'll add that my Pulp directory / volume is ~270G in size, just in case someone cares to compare upgrade completion times based on that attribute. Hope this info helps somebody out there! :-)
-- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
