EKS MountVolume.SetUp failed for volume *** : applyFSGroup failed for vol ***: input/output error

0

Hi,

Several pods in my EKS cluster are failed while initializing each's container. It happens after pulling a new version of helm chart and had no issue before upgrading - means I didn't change any network configuration including SG inbound/out bound rules. Furthermore, the issue happens for only 3 pods, the other pods in the same node are running w/o issue.

All storage blocks were attached to node, I can't find any reason/ solution to of this.

EKS에 배포되어있는 차트 업데이트 중 다음과 같은 에러메세지가 발생했습니다. 보안그룹이나 네트워크 설정같은걸 건드린게 없어서 네트워크 문제는 아닐 것 같은데 어떻게 해결할 수 있을까요? 같은 노드에 배포되어있는 다른 차트들은 문제없이 running 상태이고, 세 개의 파드에 대해서만 발생하고 있습니다.

   Type     Reason       Age                    From     Message            
   ----     ------       ----                   ----     -------                                          
Warning  FailedMount  34m (x100 over 18h)      kubelet  Unable to attach or mount volumes: unmounted volumes=[elasticsearch-master[], unattached volumes=[elasticsearch-master kube-api-access-9z2nh]: timed out waiting for the condition
Warning  FailedMount  9m51s (x399 over 19h)  kubelet  Unable to attach or mount volumes: unmounted volumes=[easticsearch-master[], unattached volumes=[kube-api-access-9z2nh elasticsearch-master]: timed out waiting for the condition
Warning  FailedMount  5m4s (x569 over 19h)    kubelet  MountVolume.SetUp failed for volume "pvc-**" : applyFSGroup failed for vol vol-08ed2be3d5de8ebb9: readdirent /var/lib/kubelet/pods/**/volumes/kubernetes.io~csi/**/mount: input/output error   
hyunie
gefragt vor einem Jahr411 Aufrufe
Keine Antworten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen