New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve driver_updates logging #4149
Improve driver_updates logging #4149
Conversation
Hello @jkonecny12! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2022-08-17 11:37:29 UTC |
@jstodola what do you think, any ideas for improvements? |
/kickstart-test --testtype smoke |
f174727
to
884a4d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! I have a few suggestions for the logging strings, but otherwise looks good.
@jkonecny12, I'm on my phone only for a while, so it's quite challenging to suggest any improvements. So, no useful feedback from my side :-) |
This change has time. I know that I will wait for you to have time, no problem with that. |
574f49a
to
01b784b
Compare
UPDATED: |
subprocess.call(["depmod", "-a"]) | ||
|
||
log.debug("load_drivers: %s", list(moddict.keys())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like a leftover.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not really left-over. The other print statements are under if
so they could be missed. It's for robustness.
/kickstart-test --testtype smoke |
This PR is stale because it has been open 60 days with no activity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thank you!
01b784b
to
803f698
Compare
UPDATED: So I changed the behavior a bit to always have a prefix |
Do you mean removing only the prefixes in console? That sounds good. |
Yes, I can leave the prefixes in the syslog but can remove them in the console. It will be problem to distinguish between debug and info message but that shouldn't be problem thought. |
@jstodola any opinion about this? |
Switching to Fedora 38 |
803f698
to
583efad
Compare
/kickstart-test --testtype smoke |
583efad
to
c67c20c
Compare
/kickstart-test --testtype smoke |
c67c20c
to
9207f2a
Compare
UPDATED:
|
/kickstart-test --testtype smoke |
- Log INFO and DEBUG messages to syslog always. - Log INFO messages to console always. - Log DEBUG messages to console only if 'inst.debug' or 'rd.debug' is on the - kernel command line.
Without these it could be real pain to solve bugs here. Most of the time special HW is required to be able to reproduce this and even with the HW there is not 100% sure that we are able to reproduce the issue. These logs will always go to journal log and with 'inst.debug' or 'rd.debug' on command line they will show up also in the console during boot. That is great help in case the code will freeze and boot process blocked. Also fix test scanning files for mount keyword. It is now used in the debug logs.
Do not test logs but where the logs are printed and if the debug mode detection is working correctly.
There were plenty of issues in readability so let's move this file into pep8 style to solve these and make the script consistent with the rest of the project.
9207f2a
to
2ac0e95
Compare
UPDATED:
Tested and it seems that everything works as it should now. |
/kickstart-test --testtype smoke |
/packit build |
Debugging of the
driver_updates
script could be a pain. To improve that we need much more logs in the whole file in a way that it won't bother users during boot. To solve that we are adding debug logs and showing them on the console only in case thatinst.debug
orrd.debug
is used.