Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KB: add "Troubleshooting: RWX Volume Fails to Be Attached Caused by Protocol not supported" #792

Merged
merged 1 commit into from
Oct 31, 2023

Conversation

derekbit
Copy link
Member

@derekbit derekbit requested a review from a team as a code owner October 27, 2023 04:25
@derekbit derekbit self-assigned this Oct 27, 2023
@netlify
Copy link

netlify bot commented Oct 27, 2023

Deploy Preview for longhornio ready!

Name Link
🔨 Latest commit efa05c2
🔍 Latest deploy log https://app.netlify.com/sites/longhornio/deploys/6540726b1249e500085538d7
😎 Deploy Preview https://deploy-preview-792--longhornio.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@jillian-maroket jillian-maroket left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@derekbit Let me know if the changes work.


## Symptoms

RWX volume fails to be attached, and the workload using the volume fails to start with these messages in logs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
RWX volume fails to be attached, and the workload using the volume fails to start with these messages in logs
Attempts to attach an RWX volume are unsuccessful, and the workload using the volume is unable to start. The logs contain the following messages:

Oct 11 07:42:23 dev-worker-1-autoscaled-small-19baf778f50efd8c k3s[1294]: Output: mount.nfs: Protocol not supported for 10.43.207.185:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c on /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/185c34f566c2eca6e8c7c6a2ede2094c076d7d25ddae286dc633eeef80551af0/globalmount
```

A RWX volume on a host with OpenSUSE MicroOS from 20231008 to 20231021) and other distros using Linux kernel 6.5.6 hits the issue.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A RWX volume on a host with OpenSUSE MicroOS from 20231008 to 20231021) and other distros using Linux kernel 6.5.6 hits the issue.
The issue applies to RWX volumes on hosts running OpenSUSE MicroOS (from 2023/10/08 to 2023/10/21) and other distributions using version 6.5.6 of the Linux kernel.


## Reason

It is a regression of NFS protocol in Linux kernel 6.5.6. As a result, a NFS client fails to connect to a NFS server inside a share-manager pod.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
It is a regression of NFS protocol in Linux kernel 6.5.6. As a result, a NFS client fails to connect to a NFS server inside a share-manager pod.
The cause of this issue is a regression of the NFS protocol in Linux kernel 6.5.6. Because of the regression, NFS clients are unable to connect to an NFS server inside a share manager pod.

Comment on lines 33 to 34
1. Upgrade the OS to a newer one with a Linux kernel >= 6.5.7
2. Downgrade the OS to a older one with a Linux kernel <= 6.5.5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Upgrade the OS to a newer one with a Linux kernel >= 6.5.7
2. Downgrade the OS to a older one with a Linux kernel <= 6.5.5
To address the issue, you can perform the following actions:
1. Upgrade the operating system to a version using Linux kernel 6.5.7 or later.
1. Downgrade the operating system to a version using Linux kernel 6.5.5 or earlier.

Copy link
Member Author

@derekbit derekbit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you @jillian-maroket .

@derekbit derekbit force-pushed the issue-6887 branch 2 times, most recently from 48bc613 to 233cf90 Compare October 31, 2023 02:10
shuo-wu
shuo-wu previously approved these changes Oct 31, 2023
…Protocol not supported`"

Longhorn 6887
Longhorn 6857

Signed-off-by: Derek Su <[email protected]>
Copy link
Contributor

@jillian-maroket jillian-maroket left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@derekbit derekbit merged commit 3ca1c70 into longhorn:master Oct 31, 2023
5 checks passed
Copy link
Member

@innobead innobead left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants