|
本文档采用自动化机器翻译技术翻译。 尽管我们力求提供准确的译文，但不对翻译内容的完整性、准确性或可靠性作出任何保证。 若出现任何内容不一致情况，请以原始 英文 版本为准，且原始英文版本为权威文本。 |
SUSE® Rancher Prime: OS Manager 支持
elemental-support 是一个实用程序，用于收集有关运行 SUSE® Rancher Prime: OS Manager 堆栈的机器的所有信息。
在排查任何 SUSE® Rancher Prime: OS Manager 节点的问题时，可以生成一个包含日志和配置文件的压缩文件。
请注意，生成的 tar.gz 文件可能包含敏感信息，例如管理集群的访问词元等。
要求
可选地，elemental-support 实用程序需要在目标机器上预装 kubectl，以便收集节点信息。这对于调试节点在 SUSE® Rancher Prime: OS Manager 升级过程中出现的问题非常有用。
使用的 kubectl 配置将从 KUBECONFIG 环境变量中查找，或者在其缺失时，将使用 /etc/rancher/k3s/k3s.yaml 或 /etc/rancher/rke2/rke2.yaml 文件。
收集信息
一旦运行，elemental-support 将在同一目录中创建压缩文件。
示例运行：
m-993369ec-4b3f-4368-86c3-1449ebf57cf2# elemental-support
I0430 11:33:38.934777 8536 log.go:42] Support version 1.3.4, commit 192dc33d, commit date 20230831
I0430 11:33:38.934865 8536 log.go:46] Getting elemental-support version
I0430 11:33:38.934918 8536 log.go:42] Copying /etc/os-release
I0430 11:33:38.935008 8536 log.go:42] Copying /etc/resolv.conf
I0430 11:33:38.935066 8536 log.go:42] Copying /etc/hostname
I0430 11:33:38.935131 8536 log.go:42] Copying /etc/rancher/agent/config.yaml
I0430 11:33:38.935174 8536 log.go:42] Copying /etc/rancher/agent/config.yaml
I0430 11:33:38.935214 8536 log.go:42] Copying dir /var/lib/elemental/agent/applied/
I0430 11:33:38.935434 8536 log.go:42] Copying dir /var/lib/rancher/agent/applied/
I0430 11:33:38.935572 8536 log.go:42] Copying dir /system/oem
I0430 11:33:38.936584 8536 log.go:42] Copying dir /oem/
I0430 11:33:38.937121 8536 log.go:42] Getting service log elemental-system-agent
I0430 11:33:38.959813 8536 log.go:42] Getting service log rancher-system-agent
I0430 11:33:38.979271 8536 log.go:42] Getting service log k3s
I0430 11:33:39.018177 8536 log.go:42] Getting service log rke2
I0430 11:33:39.036852 8536 log.go:42] Getting service log cos-setup-boot
I0430 11:33:39.053409 8536 log.go:42] Getting service log cos-setup-fs
I0430 11:33:39.068132 8536 log.go:42] Getting service log cos-setup-initramfs
I0430 11:33:39.085935 8536 log.go:42] Getting service log cos-setup-network
I0430 11:33:39.101440 8536 log.go:42] Getting service log cos-setup-reconcile
I0430 11:33:39.119528 8536 log.go:42] Getting service log cos-setup-rootfs
I0430 11:33:39.136151 8536 log.go:42] Getting service log cos-immutable-rootfs
I0430 11:33:39.153850 8536 log.go:42] Getting service log elemental
I0430 11:33:39.170564 8536 log.go:42] Getting service log NetworkManager
I0430 11:33:39.190169 8536 log.go:42] Getting elemental-cli version
I0430 11:33:39.205410 8536 log.go:42] Getting elemental-operator version
I0430 11:33:39.205621 8536 log.go:42] Getting elemental-register version
I0430 11:33:39.266263 8536 log.go:42] Found k3s kubeconfig at /etc/rancher/k3s/k3s.yaml
I0430 11:33:39.266312 8536 log.go:42] Found k3s kubectl at /usr/local/bin/kubectl
I0430 11:33:39.266320 8536 log.go:42] Getting k8s info for pods
I0430 11:33:39.770730 8536 log.go:42] Getting k8s info for secrets
I0430 11:33:39.962037 8536 log.go:42] Getting k8s info for nodes
I0430 11:33:40.118680 8536 log.go:42] Getting k8s info for services
I0430 11:33:40.280797 8536 log.go:42] Getting k8s info for deployments
I0430 11:33:40.458869 8536 log.go:42] Getting k8s info for plans
I0430 11:33:40.612138 8536 log.go:42] Getting k8s info for apps
I0430 11:33:40.787309 8536 log.go:42] Getting k8s info for jobs
I0430 11:33:40.932361 8536 log.go:42] Getting k8s logs for namespace cattle-system
I0430 11:33:41.353556 8536 log.go:42] Getting k8s logs for namespace kube-system
I0430 11:33:41.935885 8536 log.go:42] Getting k8s logs for namespace ingress-nginx
W0430 11:33:41.999345 8536 log.go:62] No pods in namespace ingress-nginx
I0430 11:33:41.999365 8536 log.go:42] Getting k8s logs for namespace calico-system
W0430 11:33:42.061902 8536 log.go:62] No pods in namespace calico-system
I0430 11:33:42.061927 8536 log.go:42] Getting k8s logs for namespace cattle-fleet-system
I0430 11:33:42.204459 8536 log.go:42] Creating final file
I0430 11:33:42.215815 8536 log.go:42] All done. File created at m-993369ec-4b3f-4368-86c3-1449ebf57cf2-2024-04-30T113342Z.tar.gz