Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionWaldirio M Pinheiro
2022-01-23 18:45:38 UTC
Description of problem:
In a fresh 6.10 or machine migrated from 6.9 to 6.10, once we execute the command "foreman-maintain content migration-stats" we are getting a traceback instead of a nice and welcome warning. Basically, we are not handling the exception.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Install a fresh 6.10 or upgrade from 6.9 -> 6.10
2. Execute the command "foreman-maintain content migration-stats"
3.
Actual results:
---
[root@ito-test ~]# foreman-maintain content migration-stats
Running Retrieve Pulp 2 to Pulp 3 migration statistics
================================================================================
Retrieve Pulp 2 to Pulp 3 migration statistics: [FAIL]
Failed executing foreman-rake katello:pulp3_migration_stats, exit status 1:
'ErbParser' is ignored.
'RubyParser' is ignored.
rake aborted!
Don't know how to build task 'katello:pulp3_migration_stats' (See the list of available tasks with `rake --tasks`)
Did you mean? katello:import_subscriptions
/opt/rh/rh-ruby27/root/usr/share/gems/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
--------------------------------------------------------------------------------
Scenario [Retrieve Pulp 2 to Pulp 3 migration statistics] failed.
The following steps ended up in failing state:
[content-migration-stats]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-migration-stats"
[root@ito-test ~]#
---
Expected results:
Nice information letting the customer know that this command is not necessary anymore, or nothing to be migrated at this moment, once the data is already in pulp3.
Additional info:
Closing this BZ as WONTFIX. 6.9 is EOL and this is not an upgrade-blocking issue. I recommend creating a KCS created if users continue to be confused by this error once they're on 6.10.