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.
Bug 2005116 - Improve output of the 'content prepare' command when an abort occurs
Summary: Improve output of the 'content prepare' command when an abort occurs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 20:10 UTC by Stephen Wadeley
Modified: 2024-05-29 20:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-29 20:19:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-25412 0 None None None 2024-05-29 19:39:46 UTC

Description Stephen Wadeley 2021-09-16 20:10:49 UTC 
Description of problem:

If a migration is stopped from a second terminal, not where the migration is running, you will see output like this in the first terminal:

2021-09-15 14:38:59 -0400: Migrating rpm content to Pulp 3 2000/25151Migration failed, You will want to investigate: https://

                                                                   ^^^ needs \n     ^^ needs full stop, or "You" should not be a capital.

"You will want to investigate:" is not good style, so rather just say "See task:"


Version-Release number of selected component (if applicable):
~]# rpm -q satellite
satellite-6.9.6-1.el7sat.noarch

How reproducible:
every time

Steps to Reproduce:
1. In terminal 1: satellite-maintain content prepare
2. In terminal 2: satellite-maintain content prepare-abort
3. Check output in terminal 1

Actual results:
2021-09-15 14:38:59 -0400: Migrating rpm content to Pulp 3 2000/25151Migration failed, You will want to investigate:

Expected results:

2021-09-15 14:38:59 -0400: Migrating rpm content to Pulp 3 2000/25151


Migration failed. See task:

Additional info:

Bug 1993682 - satellite-maintain content prepare-abort results in errors on the content prepare
Comment 1 Stephen Wadeley 2021-09-16 20:15:39 UTC 
Hi

Please also fix typo:


~]# satellite-maintain content prepare
Running Prepare content for Pulp 3

<snip>

Prepare content for Pulp 3: 
Checking for valid Katello configuraton.   <--- ton should be tion
Starting task.


Thank you
Comment 2 Brad Buckingham 2021-09-20 13:15:56 UTC 
Justin,

Should this be on Foreman Maintain or Repositories?

Thanks!
Comment 4 Brad Buckingham 2024-05-29 20:19:01 UTC 
This bugzilla only applies to Satellite 6.9.  Since 6.9 reached EOL in November 2022 and there have not been any customer cases opened, I am closing the bugzilla.  If there are any concerns with this action, please reach out to me.  Thanks!
Note You need to log in before you can comment on or make changes to this bug.