Pulp 2 migration status on Katello 3.18.1

Support
1

Problem:
Command “foreman-maintain content migration-stats” gives no output.

foreman-maintain content migration-stats

echo $?

0

Due this problem I lost courage for Pulp 2 to Pulp 3 migration procedure because it will probably lead to many troubles.

Expected outcome:

Documentation says Foreman :: Plugin Manuals
To see how much content is left to be migrated and get a time estimate, you can run:

foreman-maintain content migration-stats

This can be run between migrations to see how much has changed since the last migration.

Foreman and Proxy versions:
foreman-2.3.2-1.el7.noarch

Foreman and Proxy plugin versions:
Installed Packages

candlepin-3.1.22-1.el7.noarch
candlepin-selinux-3.1.22-1.el7.noarch
celrepp202.server.cetin-foreman-client-1.0-1.noarch
celrepp202.server.cetin-foreman-proxy-1.0-1.noarch
celrepp202.server.cetin-foreman-proxy-client-1.0-1.noarch
celrepp202.server.cetin-qpid-broker-1.0-2.noarch
celrepp202.server.cetin-qpid-client-cert-1.0-1.noarch
celrepp202.server.cetin-qpid-router-client-1.0-1.noarch
celrepp202.server.cetin-qpid-router-server-1.0-1.noarch
foreman-2.3.2-1.el7.noarch
foreman-cli-2.3.2-1.el7.noarch
foreman-debug-2.3.2-1.el7.noarch
foreman-dynflow-sidekiq-2.3.2-1.el7.noarch
foreman-installer-2.3.2-1.el7.noarch
foreman-installer-katello-2.3.2-1.el7.noarch
foreman-postgresql-2.3.2-1.el7.noarch
foreman-proxy-2.3.2-1.el7.noarch
foreman-release-2.3.2-1.el7.noarch
foreman-selinux-2.3.2-1.el7.noarch
foreman-service-2.3.2-1.el7.noarch
katello-3.18.1-1.el7.noarch
katello-ca-consumer-celrepp202.server.cetin-1.0-1.noarch
katello-certs-tools-2.7.3-1.el7.noarch
katello-client-bootstrap-1.7.5-1.el7.noarch
katello-common-3.18.1-1.el7.noarch
katello-debug-3.18.1-1.el7.noarch
katello-default-ca-1.0-1.noarch
katello-repos-3.18.1-1.el7.noarch
katello-selinux-3.5.0-1.el7.noarch
katello-server-ca-1.0-1.noarch
katello-service-3.14.1-1.el7.noarch
pulp-client-1.0-1.noarch
pulp-deb-plugins-1.10.2-1.el7.noarch
pulp-docker-plugins-3.2.8-1.el7.noarch
pulp-katello-1.0.3-1.el7.noarch
pulp-puppet-plugins-2.21.5-1.el7.noarch
pulp-puppet-tools-2.21.5-1.el7.noarch
pulp-rpm-plugins-2.21.5-1.el7.noarch
pulp-selinux-2.21.5-1.el7.noarch
pulp-server-2.21.5-1.el7.noarch
pulpcore-selinux-1.2.3-2.el7.x86_64

Distribution and version:
RHEL 7.9

Other relevant data:
Just upgraded from Katello 3.14 to 3.15, 3.16, 3.17. and finally to 3.18

2

@mdedek Thanks for reporting this to us, were there any error messages or further output?

cc @iballou

3

@mdedek if you run foreman-rake katello:pulp3_migration_stats directly and let us know how that goes, that could help us narrow down if it’s a problem with the tooling or the task itself.

4

Small update on this, it does seem like there is an issue with foreman-maintain that didn’t allow these commands to be run on katello, it’s being fixed here Fixes #31794 - allow migration scenarios on katello by jlsherrill · Pull Request #444 · theforeman/foreman_maintain · GitHub - I would recommend using that foreman-rake command directly. We are working on getting a fix shipped out!

1 Like
5

It looks better. However I am postponing migration until the process will be more tested.

# foreman-rake katello:pulp3_migration_stats

Migrated/Total RPMs: 0/276109
Migrated/Total errata: 0/1436949
Migrated/Total repositories: 0/1857

Estimated migration time based on yum content: 4 hours, 47 minutes

Note: ensure there is sufficient storage space for /var/lib/pulp/published to double in size before starting the migration process.
Check the size of /var/lib/pulp/published with 'du -sh /var/lib/pulp/published/'