Leapp doesn't log "real errors" / tracebacks #692
Labels
Comments
MichalHe
added a commit
to MichalHe/leapp
that referenced
this issue
Aug 12, 2021
…rInfo actor. (oamg#692) Further extends the test suite for the `rhsm` library module with tests that assert the functionality of all library functions used when obtaining `RHSMInfo` from the system. Also adds minimalistic tests for the `ScanSubscriptionManagerInfo` actor since almost all of its functionality is provided by the `rhsm` library module. Co-authored-by: MichalHe <mhecko@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behavior
If any actor crashes completely, leapp is not able to handle the issue nor log it (so without the console log it's not possible to see the error).
To Reproduce
Let's make any actor crash compltely and check leapp.db & /var/log/leapp/leapp-upgrade.log.
No info about the error is present inside.
Expected behavior
Crash of actor is processed by leapp and information is present in leapp.db & log files.
Addtitional info:
The text was updated successfully, but these errors were encountered: