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

Sporadic 255 exit status during mount command #1477

Open
headyj opened this issue Oct 18, 2024 · 1 comment
Open

Sporadic 255 exit status during mount command #1477

headyj opened this issue Oct 18, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@headyj
Copy link

headyj commented Oct 18, 2024

/kind bug

What happened?

For some weeks now we have sporadic issues during mount command at pod startup:

MountVolume.SetUp failed for volume "my-volume" : rpc error: code = Internal desc = Could not mount "fs-**********:/" at "/var/lib/kubelet/pods/b9a74dfa-a97c-4e2f-8f99-454be86a52b1/volumes/kubernetes.io~csi/my-volume/mount": mount failed: exit status 255 Mounting command: mount Mounting arguments: -t efs -o accesspoint=fsap-*******,tls fs-0993325f4ff5304d8:/ /var/lib/kubelet/pods/b9a74dfa-a97c-4e2f-8f99-454be86a52b1/volumes/kubernetes.io~csimy-volume/mount Output:

The pod is then stuck in ContainerCreating status. Usually killing the pod solves the problem. I cannot tell for now exactly since which version we have the problem, but we currently have the v3.0.8

It might be linked to the fact that for any reason some members of the efs-csi-node seems to use more memory than others and are hitting the memory limit (and restarting) a lot:

Screenshot from 2024-10-18 10-14-47

I don't see anything specific from the efs-csi-node pod itself except this one:

Failed to establish connection to CSI driver" err="context deadline exceeded"

How to reproduce it (as minimally and precisely as possible)?
I don't really know how exactly to reproduce the error as it only appears sporadically. I'm still investigating on that point

Anything else we need to know?:

Environment

  • Kubernetes version (use kubectl version): v1.30
  • Driver version: v3.0.8
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 18, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants