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.
Description of problem:
While migrating Pulp 2 -> Pulp 3 on Sat6.9, we should improve user experience about below points
1. After below message we flash message about different stages of migration on the same line
Prepare content for Pulp 3:
Starting task.
2021-03-31 23:26:58 +0530: Migrating content to Pulp 3 270/270
2021-04-01 00:15:46 +0530: Distribution creation 3/9
etc.
We should use new line to display new task and its progress so a user / support engineer can easily identify which all steps are completed before failure if any.
2. Migrating content to Pulp 3 step needs lot of time to complete after we display 270/270 sub-tasks completed.
For me it took almost 1 hour with limited data synced on test satellite.
2021-03-31 22:54:26 +0530: Migrating content to Pulp 3 270/270
.
.
2021-04-01 00:07:46 +0530: Migrating content to Pulp 3 270/270
It feels that this step is stuck or hung, we should proactively inform user about the time estimate or mention some thing like: This step will take a while to complete..
So users will press Ctrl + C or report a case for Hung state of "Migrating content to Pulp 3" step.
Verified.
Tested on Satellite 6.9.7 Snap 3.0
Version: rubygem-foreman_maintain-0.7.14-1.el7sat.noarch
Steps:
1. satellite-maintain content prepare
Observation:
With improved user experience of the above command, it prints progress and new task details on a new line and seems to work as mentioned in the description.
Newline behaviour is the default for the above command and if someone wants to keep the previous behaviour of one-liner output, they can use `--quiet` or `-q` option.
While testing this BZ found that content migration output is getting duplicated, which makes its output more larger, discussed this with Devel Ian Ballou, and he raised a BZ 2019390, which will be nice to have with this BZ.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Satellite Maintenance 6.9.7 Async Bug Fix Update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:4611