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:
The foreman-maintain is running everything with the shiny-spinner. As an advanced user i like to see what is going on and what it did before. Therefore I always use the --verbose for the satellite-installer already. Now with 6.5 the katello-service is also redirected to foreman-maintain and does everything on 1 line.
And secondly the logging of the upgrade process in the 'detailed' log /var/log/foreman-maintain/foreman-maintain.log is having 'unreadable' output of the satellite-installer processes due to the spinner. Log file can be reviewed in the customer case if necessary.
Version-Release number of selected component (if applicable): 6.5
How reproducible: Always
Steps to Reproduce:
1. Use foreman-maintain
Actual results:
No way to run foreman-maintain in verbose mode (at least we were not able to find something in the docs).
Expected results:
Verbose output mode for foreman-maintain.
Additional info:
Customer case will be linked and as stated the foreman-maintain.log with unreadable escape characters can be reviewed there if required.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.