Pod template File not found exception though it is exist

2

Hello, I have a driver and executor pod template files exist in s3. But when I run the job, it failed wirh FileNotFoundException: s3:/<s3bucket>/podtemplate/driver.yaml (no such file or directory) error.

Appreciate the help and suggestions here. Thank in advance

Mark
asked 5 months ago218 views
1 Answer
3
Accepted Answer

Hello,

There could a couple of reasons as mentioned below that might cause this issue,

  1. Try to use local file system directory to pass the pod template and see if that works.
  2. Check the execution role arn that submits the spark which has sufficient permission to read the pod file from S3. More details here -

https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/creating-job-execution-role.html &

https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/iam-execution-role.html

  1. Check if the mentioned S3 bucket has any bucket policy restriction that might block the read access. https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html
  2. You can leverage IAM simulator to test if the given policy can be accessible to s3 pod files - https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html
  3. Test the sample pod template job given this doc which helps to see if the issue with all the pod file template or only with problematic one - https://catalog.us-east-1.prod.workshops.aws/workshops/1f91e1d4-5587-40ff-8d5d-54fc86e0ddc1/en-US/advanced/pod-template
  4. Enable and leverage the control plane, audit logs and manager logs to see if anything reported - https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html
  5. Run this command before starting their testing. It will capture all events triggered by k8s during their testing. This will help to find if any issue in the events that initiated when launching the spark job.

kubectl get ev -n <namespace used in EMR virtual cluster> -w

AWS
SUPPORT ENGINEER
answered 5 months ago
profile pictureAWS
EXPERT
reviewed 5 months ago
  • Thank you for the detailed answer. With the help of your suggestion, I sorted the issue that occurred due to permission missing.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions