Applicable versions​

Longhorn versions = v1.1.0

Symptoms​

When Pod mounts with RWX volume, the Pod share mount directory and all of the ownership of its recurring contents are shown as nobody, but in the share-manager is shown as root.

root@ip-172-30-0-139:/home/ubuntu# kubectl exec -it rwx-test-2pml2 -- ls -l /data
total 16
drwx------ 2 nobody 42949672 16384 Mar 31 04:16 lost+found

root@ip-172-30-0-139:~# kubectl -n longhorn-system exec -it share-manager-pvc-f3775852-1e27-423f-96ab-95ccd04e4777 -- ls -l /export/pvc-f3775852-1e27-423f-96ab-95ccd04e4777
total 16
drwx------ 2 root root 16384 Mar 31 04:42 lost+found

Applicable versions​

All Longhorn versions.

Symptoms​

The pod with the volume is not starting and encounters error messages in longhorn-csi-plugin:

Applicable versions​

Existing Longhorn versions < v1.1.0 upgrade to Longhorn ≥ v1.1.0.

Symptoms​

After upgrading Longhorn to version ≥ v1.1.0, the following is encountered:

Ingress messages:

{"level":"error","msg":"vulcand/oxy/forward/websocket: Error dialing \"10.17.1.246\": websocket: bad handshake with resp: 200 200 OK","time":"2021-03-09T08:29:03Z"}

Applicable versions​

All Longhorn versions.

Symptoms​

When starting a workload pod that uses Longhorn volumes, the Longhorn UI shows that the Longhorn volumes are attached quickly, but it takes a long time for the volumes to finish mounting and for the workload to be able to start.

This issue only happens when the Longhorn volumes have many files/directories and securityContext.fsGroup is set in the workload pod as shown below:

spec:
  securityContext:
    runAsUser: 1000
    runAsGroup: 3000
    fsGroup: 2000

Applicable versions​

All Longhorn versions.

Symptoms​

When an application writes data to existing files or creates files in the mount point of a Longhorn volume, the following message is shown:

/ # cd data
/data # echo test > test
sh: can't create test: I/O error