Skip to content

[BUG] environment_check.sh does not handle differnt kernel versions in cluster correctly#5304

Description

@achims311

Describe the bug (馃悰 if you encounter this issue)

The environment_check.sh uses "uname -r" to get the kernel release and kernel config file.
But the uname -r command is always run locally, not on the node . So the checks against the kernel configuration do not work in case the node is running another kernel version than the local kernel version.

To Reproduce

Steps to reproduce the behavior:

  1. Set up a cluster on a machine not having the kernel installed which runs on the machine running the "environment_check.sh script (having the required nfs options switched on
    e.g. cluster node on server n1 with only kernel 5.19 installed and running the script on o1 with kernel 6.1 running
  2. run the environment check from the documentation:
    curl -sSfL https://raw.githubusercontent.com/longhorn/longhorn/v1.4.0/scripts/environment_check.sh | bash
  3. warn about missing nfs setup

Expected behavior

no warning should be reported

Log or Support bundle

n/A

Environment

  • Longhorn version: 1.4.0
  • Installation method (e.g. Rancher Catalog App/Helm/Kubectl): n/A
  • Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s
    • Number of management node in the cluster: 3
    • Number of worker node in the cluster: 3
  • Node config
    • OS type and version: different!
  • Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): baremetal
  • Number of Longhorn volumes in the cluster: 0 until now

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions