Skip to content
This repository has been archived by the owner. It is now read-only.

AMIs don't have ENA enabled #1853

Closed
crawford opened this issue Mar 7, 2017 · 4 comments
Closed

AMIs don't have ENA enabled #1853

crawford opened this issue Mar 7, 2017 · 4 comments

Comments

@crawford
Copy link
Member

@crawford crawford commented Mar 7, 2017

Issue Report

Bug

Container Linux Version

CoreOS-stable-1298.5.0-hvm (ami-fd92109d)

Environment

EC2

Other Information

User reported that we were missing the instance attribute.

@euank
Copy link
Contributor

@euank euank commented Mar 7, 2017

This might not be as trivial as it seems since, iirc, the ancient ec2-utils package we're using doesn't have the flag we need. It didn't the last time I glanced at this.

Changing it to use the aws cli (or getting plume in shape) does fix the problem, but isn't quite so trivial.

Hopefully my memory is wrong or ec2-utils has been updated and does have the flag.

@bgilbert bgilbert self-assigned this Mar 31, 2017
@bgilbert bgilbert removed this from the Container Linux Alpha 1354.0.0 milestone Apr 3, 2017
@bgilbert
Copy link
Member

@bgilbert bgilbert commented Apr 11, 2017

Fixed in coreos/mantle#540.

@bgilbert bgilbert closed this Apr 11, 2017
@joelittlejohn
Copy link

@joelittlejohn joelittlejohn commented Jan 3, 2018

@bgilbert do you know which version of the CoreOS Stable HVM AMI is required in order to have ENA enabled?

@joelittlejohn
Copy link

@joelittlejohn joelittlejohn commented Jan 3, 2018

Sorry, answered my own question. Looks like it's CoreOS-stable-1353.6.0-hvm (this is the first AMI that has EnaSupport: true).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.