Skip to content

Commit a2807e3

Browse files
committed
Adding Nessie to troubleshooting docs
1 parent 1b3567c commit a2807e3

File tree

2 files changed

+2
-6
lines changed

2 files changed

+2
-6
lines changed

asciidoc/troubleshooting/collecting-diagnostics-for-support.adoc

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,6 @@ When contacting SUSE Support, providing comprehensive diagnostic information is
4242
* *For SL Micro*: Check the https://documentation.suse.com/sle-micro/5.5/html/SLE-Micro-all/cha-adm-support-slemicro.html[SUSE Linux Micro Troubleshooting Guide] documentation on how to gather system information for support with `supportconfig`.
4343
* *For RKE2/Rancher*: Check the https://www.suse.com/support/kb/doc/?id=000020191[The Rancher v2.x Linux log collector script] article to run The Rancher v2.x Linux log collector script.
4444
45-
////
46-
4745
* *Nessie*: Nessie is a powerful diagnostic tool designed to collect logs and configuration data from SUSE Edge environments. It gathers comprehensive information from both the host system and Kubernetes clusters, making it invaluable for troubleshooting and support. To collect logs from a SUSE Edge cluster, connect to any of the control plane nodes and run:
4846
+
4947
[,shell]
@@ -54,15 +52,13 @@ podman run --privileged \
5452
-v /run/systemd:/run/systemd:ro \
5553
-v /etc/machine-id:/etc/machine-id:ro \
5654
-v /tmp/nessie-logs:/tmp/cluster-logs \
57-
ghcr.io/gagrio/nessie
55+
registry.suse.com/edge/3.4/nessie:1.0.0
5856
----
5957
+
6058
[NOTE]
6159
====
6260
Adjust the paths of the `k3s.yaml/rke2.yaml` file if needed. See https://github.com/suse-edge/support-tools/blob/main/nessie/README.md[Nessie] for more information.
6361
====
6462
65-
////
66-
6763
.Contact Support
6864
Please check the article available at https://www.suse.com/support/kb/doc/?id=000019452[How-to effectively work with SUSE Technical Support] and the support handbook located at https://www.suse.com/support/handbook/[SUSE Technical Support Handbook] for more details on how to contact SUSE support.

asciidoc/troubleshooting/general-troubleshooting-principles.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,4 +25,4 @@ Before diving into component-specific issues, consider these general principles:
2525
* *Isolate the problem*: Try to narrow down the issue to a specific component or layer (for example, network, storage, OS, Kubernetes, Metal^3^, Ironic,...).
2626
* *Documentation*: Always refer to the official https://documentation.suse.com/suse-edge/[SUSE Edge documentation] and also upstream documentation for detailed information.
2727
* *Versions*: SUSE Edge is an opinionated and thoroughly tested version of different SUSE components. The versions of each component per SUSE Edge release can be observed in the https://documentation.suse.com/suse-edge/support-matrix/html/support-matrix/index.html[SUSE Edge support matrix].
28-
* *Known issues*: For each SUSE Edge release there is a “Known issues” section on the release notes that contains information of issues that will be fixed on future releases but can affect the current one.
28+
* *Known issues*: For each SUSE Edge release there is a “Known issues” section on the release notes that contains information of issues that will be fixed on future releases but can affect the current one.

0 commit comments

Comments
 (0)