-
Notifications
You must be signed in to change notification settings - Fork 190
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
USHIFT-1022: Add sos debugging tips to docs #1562
Conversation
There was a ticket for the sos work. It would be good to link this PR to that ticket, for future reference. |
docs/debugging_tips.md
Outdated
@@ -35,19 +35,135 @@ configuration, diagnostic, and troubleshooting data to be provided to Red Hat Te | |||
|
|||
> See [Generating sos reports for technical support](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/generating_sos_reports_for_technical_support/index) for more information on the `sos` utility usage. |
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.
We support RHEL 9 now
> See [Generating sos reports for technical support](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/generating_sos_reports_for_technical_support/index) for more information on the `sos` utility usage. | |
> See [Generating sos reports for technical support](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/getting_the_most_from_your_support_experience/generating-an-sos-report-for-technical-support_getting-the-most-from-your-support-experience) for more information on the `sos` utility usage. |
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.
Done.
docs/debugging_tips.md
Outdated
> See [documentation](https://github.com/sosreport/sos) for further information on `sos` utility. | ||
|
||
Sos tool is composed of different plugins for tailored retrieval of information from different applications. | ||
A MicroShift specific plugin has been added from sos version 4.5.1, being able to gather: |
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.
A MicroShift specific plugin has been added from sos version 4.5.1, being able to gather: | |
A MicroShift specific plugin has been added from sos version 4.5.1 and it can gather the following data: |
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.
Done.
docs/debugging_tips.md
Outdated
Plugin is automatically enabled as soon as it detects any of the following conditions: | ||
* MicroShift RPMs being installed. | ||
* MicroShift systemd service being present, whether running or not. | ||
* MicroShift ovnk pods running. |
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.
Plugin is automatically enabled as soon as it detects any of the following conditions: | |
* MicroShift RPMs being installed. | |
* MicroShift systemd service being present, whether running or not. | |
* MicroShift ovnk pods running. | |
The plugin is automatically enabled when it detects any of the following conditions: | |
* MicroShift RPMs are installed | |
* MicroShift systemd service is present, whether running or not | |
* MicroShift ovnk pods are running |
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.
Done.
* MicroShift systemd service being present, whether running or not. | ||
* MicroShift ovnk pods running. | ||
|
||
For more information on the plugin design and output format, please check the [enhancement proposal](https://github.com/openshift/enhancements/blob/master/enhancements/microshift/microshift-supportability-tools.md). |
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.
I'm not sure we should reference the ER from the docs. It can be confusing because the plugin will evolve and eventually not be like described in the ER.
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.
I included it because there is quite some relevant details there. Arent the ER's supposed to evolve with the implementation, if changes are significant enough?
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 just, these are user docs and ERs are very technical. A developer should be able to find the ER without the reference.
docs/debugging_tips.md
Outdated
$ sos report --list-profiles | ||
|
||
sosreport (version 4.3) | ||
|
||
The following profiles are available: | ||
|
||
boot boot, devices, dracut, grub2, services, systemd, udev | ||
cluster conntrack | ||
container cgroups, containers_common, crio, podman, selinux | ||
debug hts, kdump | ||
desktop soundcard, x11 | ||
hardware ata, block, crypto, devices, hardware, kernel, logs, | ||
memory, multipath, networking, networkmanager, ntb, | ||
openhpi, pci, processor, scsi, soundcard, teamd, udev, | ||
udisks, usb, x11 | ||
identity krb5, ldap, login, nis, pam, ssh, sssd, sudo | ||
java jars | ||
kernel ebpf, kernel, system | ||
memory memory, processor | ||
microshift microshift, microshift_ovn | ||
network conntrack, ebpf, firewall_tables, firewalld, | ||
networking, networkmanager, nss, openssl, teamd, | ||
unbound | ||
openshift selinux | ||
packagemanager dnf, rpm, subscription_manager, yum | ||
performance tuned | ||
perl perl | ||
sap vhostmd | ||
security auditd, nss, openssl, pam, selinux, ssh, sssd | ||
services chrony, nis, ssh, sssd, systemd, sysvipc, unbound | ||
storage ata, block, devicemapper, devices, filesys, iscsi, | ||
logs, lvm2, md, multipath, scsi, xfs | ||
sysmgmt dnf, insights, ldap, subscription_manager, yum | ||
system anaconda, anacron, auditd, boot, cgroups, chrony, | ||
console, cron, crypto, dbus, devices, dnf, ebpf, | ||
firewall_tables, hardware, host, i18n, insights, kdump, | ||
kernel, krb5, kvm, ldap, libraries, libvirt, login, | ||
logrotate, logs, memory, multipath, networking, | ||
networkmanager, openhpi, pam, pci, process, processor, | ||
python, release, rpm, selinux, services, ssh, | ||
subscription_manager, sudo, system, systemd, sysvipc | ||
tuned, udev, udisks, unbound, vhostmd, yum | ||
virt kvm, libvirt, vhostmd, xen | ||
webserver perl | ||
|
||
24 profiles, 91 plugins |
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.
Let's shorten the list. Alternatively, just grep for microshift to show the appropriate line
$ sos report --list-profiles | |
sosreport (version 4.3) | |
The following profiles are available: | |
boot boot, devices, dracut, grub2, services, systemd, udev | |
cluster conntrack | |
container cgroups, containers_common, crio, podman, selinux | |
debug hts, kdump | |
desktop soundcard, x11 | |
hardware ata, block, crypto, devices, hardware, kernel, logs, | |
memory, multipath, networking, networkmanager, ntb, | |
openhpi, pci, processor, scsi, soundcard, teamd, udev, | |
udisks, usb, x11 | |
identity krb5, ldap, login, nis, pam, ssh, sssd, sudo | |
java jars | |
kernel ebpf, kernel, system | |
memory memory, processor | |
microshift microshift, microshift_ovn | |
network conntrack, ebpf, firewall_tables, firewalld, | |
networking, networkmanager, nss, openssl, teamd, | |
unbound | |
openshift selinux | |
packagemanager dnf, rpm, subscription_manager, yum | |
performance tuned | |
perl perl | |
sap vhostmd | |
security auditd, nss, openssl, pam, selinux, ssh, sssd | |
services chrony, nis, ssh, sssd, systemd, sysvipc, unbound | |
storage ata, block, devicemapper, devices, filesys, iscsi, | |
logs, lvm2, md, multipath, scsi, xfs | |
sysmgmt dnf, insights, ldap, subscription_manager, yum | |
system anaconda, anacron, auditd, boot, cgroups, chrony, | |
console, cron, crypto, dbus, devices, dnf, ebpf, | |
firewall_tables, hardware, host, i18n, insights, kdump, | |
kernel, krb5, kvm, ldap, libraries, libvirt, login, | |
logrotate, logs, memory, multipath, networking, | |
networkmanager, openhpi, pam, pci, process, processor, | |
python, release, rpm, selinux, services, ssh, | |
subscription_manager, sudo, system, systemd, sysvipc | |
tuned, udev, udisks, unbound, vhostmd, yum | |
virt kvm, libvirt, vhostmd, xen | |
webserver perl | |
24 profiles, 91 plugins | |
$ sos report --list-profiles | |
sosreport (version 4.3) | |
The following profiles are available: | |
... | |
... | |
microshift microshift, microshift_ovn | |
... | |
... | |
24 profiles, 91 plugins |
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.
Done.
Log into the host running MicroShift and execute the following command to generate an obfuscated | ||
report that should not contain sensitive information (in this example only microshift plugin was | ||
enabled. Your system's output may vary): | ||
```bash |
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.
Can we please shorten the output? Let's think what is relevant for the users to see. We may even want to skip it completely.
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.
Done.
The report archives can be found in the `/var/tmp/sosreport-*` files. | ||
Log into the host running MicroShift and execute the following command to generate an obfuscated | ||
report that should not contain sensitive information (in this example only microshift plugin was | ||
enabled. Your system's output may vary): |
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.
Do you want to update the command below to explicitly run microshift plugin only? This way, we should not need to explain about different output, etc.
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.
Done.
docs/debugging_tips.md
Outdated
|
||
The output file was generated in `/var/tmp/` dir, and a checksum file is also generated. |
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.
The output file was generated in `/var/tmp/` dir, and a checksum file is also generated. | |
The output file and its checksum are generated in `/var/tmp/` directory. |
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.
Done.
docs/debugging_tips.md
Outdated
$ sudo ls -tr /var/tmp/sosreport-* | tail -2 | ||
/var/tmp/sosreport-host0-2022-11-24-pvbcaji-obfuscated.tar.xz | ||
/var/tmp/sosreport-host0-2022-11-24-pvbcaji-obfuscated.tar.xz.sha256 | ||
$ sudo ls -tr /var/tmp/ |
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.
Do we want to leave the original command to only display the last two archives? The current command will display everything in the /var/tmp
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.
Fair enough, it should be mostly empty though.
@pacevedom: This pull request references USHIFT-1022 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ggiguash, pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@pacevedom: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Which issue(s) this PR addresses:
Closes #