Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
--upload feature does not provide much (verbose) logging, esp. when something goes wrong (or for uploading via sftp protocol).
Let enhance that logging after some agreement when&what shall be logged but is currently missing.
Version-Release number of selected component (if applicable):
sos-4.2-2
How reproducible:
100%
Steps to Reproduce:
sos report -vvv --upload [--upload-protocol=sftp]
.. and various scenarios wrt. success/failure/cause-of-failure
Actual results:
minimal (debug) logs
Expected results:
more (debug) logs
Additional info:
This is going to be difficult to really do well, as our (file) logging is closed by the time we get to the upload attempt:
https://github.com/sosreport/sos/blob/main/sos/report/__init__.py#L1409
We can build out some console messaging, but what specifically are you looking for more information on to report? Currently if anything in `Policy.upload_archive()` fails we raise an appropriately (hopefully, anyways) descriptive exception whose message is then printed to console.
(In reply to Jake Hunsaker from comment #2)
> This is going to be difficult to really do well, as our (file) logging is
> closed by the time we get to the upload attempt:
>
> https://github.com/sosreport/sos/blob/main/sos/report/__init__.py#L1409
.. and that file logging must be closed as the logfile is contained in the tarball we attempt to upload.
>
> We can build out some console messaging, but what specifically are you
> looking for more information on to report? Currently if anything in
> `Policy.upload_archive()` fails we raise an appropriately (hopefully,
> anyways) descriptive exception whose message is then printed to console.
This went out from discussion with Miroslav, raising needinfo on him when&what to more debug-log.
Comment 7RHEL Program Management
2023-05-16 07:28:27 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Hello,
this bug is assumed to be fixed in errata https://access.redhat.com/errata/RHBA-2023:3801 so I am closing this BZ as fixed in current release.
If you feel otherwise, please reopen the BZ and provide details what is missing.