Open wfeldt opened 1 year ago
Collecting those tarballs if they already exist seems reasonable. We already do this for hb_report and spacewalk.
save_y2logs
has a predictable naming scheme that's reliable, but getsysinfo
is rather generic.
I'm worried collecting the file from getsysinfo. /tmp/
Running hwinfo --all averages about 6.5 seconds longer to complete compared to hwinfo -braille that supportconfig currently runs. If the information is significant, then the change can be made.
What about using -A to get all information and have supportconfig run save_y2logs, getsysinfo and hwinfo --all, or at least the first two. That way we don't gather the additional information needlessly and it will take less time to run supportconfig.
I have addressed the hwinfo in hardware.txt in bsc#1208928. I will now consider getsysinfo and save_y2logs separately.
The info
supportconfig
collects is usually not sufficient to resolve issues in the installer or hardware detection area (hwinfo
).This typically leads to a back-and-forth with customers until the necessary data has been provided. This process can by trying for both sides and is easily avoided.
For this reason I would suggest to include these three items in the default
supportconfig
output:save_y2logs
createsgetsysinfo
createshwinfo --all --log=xxx.log
Note that fragments of the above are already provided but for efficient debugging it is also vital that information is provided in a way developers expect and can readily use.