This repository has been archived by the owner on Jun 10, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 142
New NVMe disks on AWS are not supported #452
Comments
Do you know if there's a recommended way to detect if the instance is using NVMe backed instances? I've been using the following patch successfully on c5 instances for some time, but it feels quite kludgy. Listing instance types would be far from optimal also as new instance types would need to be added quite often.
|
john-pierce
added a commit
to john-pierce/bootstrap-vz
that referenced
this issue
Jul 12, 2018
Fixes: andsens#452 Adds support for building on EC2 hosts that have NVMe EBS devices. Introduces the DescribeInstances permission requirement for the calling role. Changes the device naming logic on the host during build time. - The new target volume will be mounted with the highest available DeviceName in the BlockDeviceMapping object, taking care to avoid assignments that also are allocated at launch to ephemeral devices (C5d, I3, F1, and M5d currently). - The system device name will be identifed by the difference between the existing block devices prior to and after the AttachVolume call has finished. This race condition already existed with the previous logic.
john-pierce
added a commit
to john-pierce/bootstrap-vz
that referenced
this issue
Jul 15, 2018
Fixes: andsens#452 Adds support for building on EC2 hosts that have NVMe EBS devices. Introduces the DescribeInstances permission requirement for the calling role. Changes the device naming logic on the host during build time. - The new target volume will be mounted with the highest available DeviceName in the BlockDeviceMapping object, taking care to avoid assignments that also are allocated at launch to ephemeral devices (C5d, I3, F1, and M5d currently). - The system device name will be identifed by the difference between the existing block devices prior to and after the AttachVolume call has finished. This race condition already existed with the previous logic.
john-pierce
added a commit
to john-pierce/bootstrap-vz
that referenced
this issue
Jul 15, 2018
Fixes: andsens#452 Adds support for building on EC2 hosts that have NVMe EBS devices. Introduces the DescribeInstances permission requirement for the calling role. Changes the device naming logic on the host during build time. - The new target volume will be mounted with the highest available DeviceName in the BlockDeviceMapping object, taking care to avoid assignments that also are allocated at launch to ephemeral devices (C5d, I3, F1, and M5d currently). - The system device name will be identifed by the difference between the existing block devices prior to and after the AttachVolume call has finished. This race condition already existed with the previous logic.
john-pierce
added a commit
to john-pierce/bootstrap-vz
that referenced
this issue
Jul 16, 2018
Fixes: andsens#452 Adds support for building on EC2 hosts that have NVMe EBS devices. Introduces the DescribeInstances permission requirement for the calling role. Changes the device naming logic on the host during build time. - The new target volume will be mounted with the highest available DeviceName in the BlockDeviceMapping object, taking care to avoid assignments that also are allocated at launch to ephemeral devices (C5d, I3, F1, and M5d currently). - The system device name will be identifed by the difference between the existing block devices prior to and after the AttachVolume call has finished. This race condition already existed with the previous logic.
john-pierce
added a commit
to john-pierce/bootstrap-vz
that referenced
this issue
Jul 16, 2018
Fixes: andsens#452 Adds support for building on EC2 hosts that have NVMe EBS devices. Introduces the DescribeInstances permission requirement for the calling role. Changes the device naming logic on the host during build time. - The new target volume will be mounted with the highest available DeviceName in the BlockDeviceMapping object, taking care to avoid assignments that also are allocated at launch to ephemeral devices (C5d, I3, F1, and M5d currently). - The system device name will be identifed by the difference between the existing block devices prior to and after the AttachVolume call has finished. This does not address the race condition identified in andsens#459.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I just tried building an image using a new M5 instance, which failed during a partitioning step. I see bootstrap-vz expects disks to be in the
/dev/xvd + letter
or /dev/sd + letter` format, while the newest AWS generations have moved to NVMe: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.htmlSome extra information on the error:
The text was updated successfully, but these errors were encountered: