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:
"satellite-maintain content prepare" is not logging the information in the log file

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Execute the command "satellite-maintain content prepare"

Actual results:
Nothing is logged

Expected results:
Keep the tracking of everything that was done

Additional info:

Hi Waldirio,

Can you provide more details on the logging that you are looking for?

Is it detailed logging on the process of the migration?
Is it logs related to errors that might occur as an outcome of running the migration?

Thanks in advance!

Hello Brad,

During the migration process, should be interesting to have a single log with the whole information, for example, when we start the content migration, we can see in the terminal all the outputs, also, if something happen (error), it should be interesting to be in the log as well.

At this moment, I believe we don't have any log with the whole content migration information, which is hard when doing the troubleshooting process.

Please, let me know if that makes sense. If you need anything else, I'll be more than glad to help.

Thank you
Waldirio

Closing this BZ as WONTFIX. 6.9 is EOL and this is not an upgrade-blocking issue.