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

[CSI, AWS EBS] - Volume Setup Failure on t3 instances. #7764

Closed
angrycub opened this issue Apr 21, 2020 · 3 comments
Closed

[CSI, AWS EBS] - Volume Setup Failure on t3 instances. #7764

angrycub opened this issue Apr 21, 2020 · 3 comments

Comments

@angrycub
Copy link
Contributor

Nomad version

Nomad v0.11.0 (5f8fe0a)

Operating system and Environment details

Ubuntu 18.04 on Amazon t3.small instances

Issue

When I attempt to mount a volume into a job I receive the following error event:

Recent Events:
Time                  Type           Description
2020-04-21T13:53:07Z  Setup Failure  failed to setup alloc: pre-run hook "csi_hook" failed: rpc error: code = Internal desc = Failed to find device path /dev/xvdba. nvme path "/dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_mysql" not found

I would expect this path to be /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_«amazon volume id»

Reproduction steps

Run a dev agent on a AWS t3 instance. Follow the guide process on learn

Job file (if appropriate)

included in the learn scenario

@angrycub
Copy link
Contributor Author

This looks to be the same issue as #7568, and I tested and verified that #7754 solves it.

@tgross
Copy link
Member

tgross commented Apr 22, 2020

Thanks @angrycub! That'll go out in the upcoming 0.11.1 release.

@tgross tgross closed this as completed Apr 22, 2020
@github-actions
Copy link

github-actions bot commented Nov 8, 2022

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants