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
[plugins] investigate exception propagation from _copy_dir() #480
Comments
Where is the original backtrace? That would tell us why it was not caught. |
cat sos_logs/kernel-plugin-errors.txt |
Thanks! |
Two possible things here - am in a meeting right now but I'll try to update later. |
I'm currently looking at just moving that bit to walk - BryanQuigley@82633f5 seems to work in my testing so far.. need to add reporting for errors.. It may actually be possible to move all of copy_path to walk but testing that was complicated... |
@slashdd in 3.7 testing I refound this for LXD containers. Don't see why it moved from kernel->system though (was system in 3.6 afaict) sos_logs/system-plugin-errors.txt |
Closing as I believe this has been handled in previous versions with regards to container detection and execution support, but perhaps most notably e10473d to log the exception rather than allow it to be uncaught. |
Commit a668851 works around a problem that causes sos to abruptly terminate in Docker container environments:
Handling the OSError in
_copy_dir()
itself gives the desired behaviour but it's unclear why this wasn't already caught (and either re-raised or logged but allowing the rest of the sos run to continue) by the existing high-level exception handling.The text was updated successfully, but these errors were encountered: