-
Notifications
You must be signed in to change notification settings - Fork 67
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
Invalid device name /dev/sdf1 on EC2 spot request using an EBS snapshot #37
Comments
@jldonovan3 – did you ever figure this out? I am running into the same issue. |
@jldonovAfter a bit more digging, I found this in the AWS docs:
Changing the device naming to exclude the trailing number seems to have fixed the problem for me. See details on the commit or check out my fork, which fixes a few other things as well. I'd be happy to submit a pull request but it doesn't appear that this repo is currently being maintained. |
@gwhobbs Sorry about the delayed reply, had to dig up some stuff since this was a while ago. But yes, I think you came to the same solution I think I came up with. There's an bunch of device names in brenda/utils.py, and the first one it takes is I removed the number from the first device name from a local branch I was messing around with:
Thanks for updating the tool! I'm not a programmer by trade and only tinkered with it to get it to do what I needed. Glad to see somebody's taking it under their wing. |
@jldonovan3 – thanks for the reply! I'm glad you were able to find a solution at the time. Yeah, this is a super useful tool but there are a few issues that seem to have crept up over the years. |
I am requesting spot instances that have an EBS snapshot attached that contains project files to render. I get a
bad-parameters
failure on the spot request with the following state:failed: Invalid device name /dev/sdf1
The output from thebrenda-run
command gives me my Snapshot ID, and what appears to be the device mapping:Project EBS snapshot: [('snap-xxxxxxxx', '/dev/sdf1')]
Would the spot requests be failing because brenda (or boto) is device mapping to something AWS is saying is invalid? brenda is assigning
block_device_map
tobdm
, and in brenda/aws.py,bdm
is usingboto.ec2.blockdevicemapping.BlockDeviceMapping()
from brenda/aws.py:
In the file used to start up the instances, brenda/run.py,
bdm
is given as theblock_device_map
from brenda/run.py:
It seems similar to what's going on in this thread, but I'm not sure how to implement the solution in my case with brenda.
boto version: 2.49.0
Appreciate any help!
The text was updated successfully, but these errors were encountered: