[BUG] Update the Longhorn document in Using the Environment Check Script

[roger-ryao]

Describe the bug

After execuetd using-the-environment-check-script , I found out the console output different from the document.

Quick Installation

Example result on the document

daemonset.apps/longhorn-environment-check created
waiting for pods to become ready (0/3)
all pods ready (3/3)
  MountPropagation is enabled!
cleaning up...
daemonset.apps "longhorn-environment-check" deleted
clean up complete

Since v1.3.1, console output result:

[INFO]  Required dependencies are installed.
[INFO]  Waiting for longhorn-environment-check pods to become ready (0/3)...
[INFO]  All longhorn-environment-check pods are ready (3/3).
[INFO]  Required packages are installed.
[INFO]  Cleaning up longhorn-environment-check pods...
[INFO]  Cleanup completed.

To Reproduce

To run script:
curl -sSfL https://raw.githubusercontent.com/longhorn/longhorn/v1.4.0/scripts/environment_check.sh | bash

Expected behavior

We need to update the document since 1.3.1+.

Log or Support bundle

N/A

Environment

• Longhorn version:1.3.1
• Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
• Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:n/a
  • Number of management node in the cluster:1
  • Number of worker node in the cluster:3
• Node config
  • OS type and version: ubuntu 20.04
  • CPU per node: 4 cores
  • Memory per node:8GB
  • Disk type(e.g. SSD/NVMe):n/a
  • Network bandwidth between the nodes:n/a
• Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): KVM
• Number of Longhorn volumes in the cluster:

Additional context

N/A

[roger-ryao]

• 1.2.5
• 1.2.6-rc1
• 1.3.1
• 1.3.2
• master

[roger-ryao]

Hi @weizhe0422 :
After I verified it, we lost commit on the 1.3.2 & 1.3.3-dev.

[weizhe0422]

Hi @Lichiehyao, the 1.3.2 and 1.3.3 has updated. Please help to verify it. Thanks a lot.

• v1.3.2
  
• v1.3.3
  

[roger-ryao]

• 1.2.5
• 1.2.6
• 1.3.1
• 1.3.2
• 1.3.3
• 1.4.0
  Result Passed