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

Error settings up EBS volume #109

Closed
yoanisgil opened this issue Dec 27, 2015 · 7 comments
Closed

Error settings up EBS volume #109

yoanisgil opened this issue Dec 27, 2015 · 7 comments
Labels
Milestone

Comments

@yoanisgil
Copy link

Hi there,

I'm trying to configure OSD to use an EBS volume however when I launch the osd daemon I get this error:

osd -d -f /usr/local/etc/osd-config.yml
INFO[0000] Starting volume driver: aws
WARN[0000] Unable to start volume driver: aws, Error querying AWS metadata for key placement/availability-zone: Code 404 returned for url http://169.254.169.254/latest/meta-data/placement/availability-zone

the config.yml file looks like this:

sd:
  drivers:
      aws:
        aws_access_key_id: AWS_KEY_ID
        aws_secret_access_key: AWS_SECRET_KEY

any ideas?

@jvinod
Copy link
Contributor

jvinod commented Jan 1, 2016

Could you try to wget that URL directly from your ec2 instance? That might
give some clues..

On Sunday, December 27, 2015, Yoanis Gil notifications@github.com wrote:

Hi there,

I'm trying to configure OSD to use an EBS volume however when I launch the
osd daemon I get this error:

osd -d -f /usr/local/etc/osd-config.yml
INFO[0000] Starting volume driver: aws
WARN[0000] Unable to start volume driver: aws, Error querying AWS metadata for key placement/availability-zone: Code 404 returned for url http://169.254.169.254/latest/meta-data/placement/availability-zone

the config.yml file looks like this:

sd:
drivers:
aws:
aws_access_key_id: AWS_KEY_ID
aws_secret_access_key: AWS_SECRET_KEY

any ideas?


Reply to this email directly or view it on GitHub
#109.

@yoanisgil
Copy link
Author

@jvinod sorry for the very late response. I believe that URL is coming straight from the code. See here:

https://github.com/libopenstorage/openstorage/blob/master/volume/drivers/aws/aws.go#L166

@jvinod
Copy link
Contributor

jvinod commented Jan 20, 2016

Yes, I understand - I was wondering if you could directly run

curl -L http://169.254.169.254/latest/meta-data/placement/availability-zone
from
your ec2 instance and post the results - that's aws special url
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html

On Tue, Jan 19, 2016 at 7:46 PM, Yoanis Gil notifications@github.com
wrote:

@jvinod https://github.com/jvinod sorry for the very late response. I
believe that URL is coming straight from the code. See here:

https://github.com/libopenstorage/openstorage/blob/master/volume/drivers/aws/aws.go#L166


Reply to this email directly or view it on GitHub
#109 (comment)
.

@jvinod
Copy link
Contributor

jvinod commented Jan 25, 2016

Ping @yoanisgil - any news?

@yoanisgil
Copy link
Author

@jvinod sorry for the delay. This is the output:

curl -L http://169.254.169.254/latest/meta-data/placement/availability-zone
us-west-2b

so it looks this URL is only available from AWS internal network. Right?

@jvinod
Copy link
Contributor

jvinod commented Jan 25, 2016

Oh yes. EBS volume driver is for AWS internal network :)

On Mon, Jan 25, 2016 at 1:09 PM, Yoanis Gil notifications@github.com
wrote:

@jvinod https://github.com/jvinod sorry for the delay. This is the
output:

curl -L
http://169.254.169.254/latest/meta-data/placement/availability-zone
us-west-2b

so it looks this URL is only available from AWS internal network. Right?


Reply to this email directly or view it on GitHub
#109 (comment)
.

@erickhan erickhan added this to the v1.1 milestone Mar 8, 2017
@lpabon
Copy link
Member

lpabon commented Nov 13, 2017

Closing since it has had no update for more than 6 months. Please reopen if needed.

@lpabon lpabon closed this as completed Nov 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants