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

Improve EFS mounting process #28

Open
giantcow opened this issue Jan 9, 2023 · 0 comments
Open

Improve EFS mounting process #28

giantcow opened this issue Jan 9, 2023 · 0 comments

Comments

@giantcow
Copy link
Contributor

giantcow commented Jan 9, 2023

Currently, when a new cluster is created, there will be 3-4 tasks that fail to start because they cannot mount EFS. Eg.:
Resourceinitializationerror: failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-<id>.efs.us-east-1.amazonaws.com" - check that your file system ID is correct, and ensure that the VPC has an EFS mount target for this file system ID. See https://docs.aws.amazon.com/console/efs/mount-dns-name for more detail. Attempting to lookup mount target ip address using botocore. Failed to import necessary dependency botocore, please install botocore first. : unsuccessful EFS utils command execution; code: 1

  • Only happens when a new EFS file system is created
  • Cannot just add a delay, because then we'd artificially add delay when it would be working normally
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

No branches or pull requests

1 participant