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

provider/aws: fix root_block_device for odd AMIs #2271

Merged
merged 1 commit into from
Jun 23, 2015

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Jun 8, 2015

Some AMIs have a RootDeviceName like "/dev/sda1" that does not appear as a
DeviceName in the BlockDeviceMapping list (which will instead have
something like "/dev/sda")

While this seems like it breaks an invariant of AMIs, it ends up working
on the AWS side, and AMIs like this are common enough that we need to
special case it so Terraform does the right thing.

Our heuristic is: if the RootDeviceName does not appear in the
BlockDeviceMapping, assume that the DeviceName of the first
BlockDeviceMapping entry serves as the root device.

fixes #2224

@phinze phinze force-pushed the b-root-block-device-ami-mismatch branch 2 times, most recently from e55926e to 3987f9e Compare June 8, 2015 16:45
@mitchellh
Copy link
Contributor

What a world. LGTM

Some AMIs have a RootDeviceName like "/dev/sda1" that does not appear as a
DeviceName in the BlockDeviceMapping list (which will instead have
    something like "/dev/sda")

While this seems like it breaks an invariant of AMIs, it ends up working
on the AWS side, and AMIs like this are common enough that we need to
special case it so Terraform does the right thing.

Our heuristic is: if the RootDeviceName does not appear in the
BlockDeviceMapping, assume that the DeviceName of the first
BlockDeviceMapping entry serves as the root device.

fixes #2224
@phinze phinze force-pushed the b-root-block-device-ami-mismatch branch from 3987f9e to 020dc03 Compare June 23, 2015 14:01
phinze added a commit that referenced this pull request Jun 23, 2015
provider/aws: fix root_block_device for odd AMIs
@phinze phinze merged commit 86b9f5a into master Jun 23, 2015
@phinze phinze deleted the b-root-block-device-ami-mismatch branch June 23, 2015 19:31
@ghost
Copy link

ghost commented May 2, 2020

I'm going to lock this issue because it has been closed for 30 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.

@ghost ghost locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants