Network Error when accessing 169.254.169.254

247 views
Skip to first unread message

Daniel Watrous

unread,
Aug 6, 2014, 12:26:24 PM8/6/14
to vcap...@cloudfoundry.org
I'm very new to CloudFoundry and I'm trying to go through this sequence to validate that my OpenStack will work with CloudFoundry:

I can't tell if the step "Can you access OpenStack metadata service from a virtual machine?" really intends for me to use that specific IP address of if I'm supposed to have an IP address for my openstack that provides that metadata service...

When try to run the cURL command, I get this after a long delay:

watrous@d9u0093:~$ curl http://169.254.169.254
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (tcp_error)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
A communication error occurred: "Operation timed out"
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>

Any help is appreciated...

Koper, Dies

unread,
Aug 6, 2014, 7:30:21 PM8/6/14
to vcap...@cloudfoundry.org

Hi Daniel,

 

You have to use that specific address.

http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html

 

There are some settings to check at the end of the page above.

 

Regards,

Dies Koper

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/28085758-d7ef-439e-8277-b70b83a00614%40cloudfoundry.org.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.



 

Daniel Watrous

unread,
Aug 7, 2014, 3:33:26 PM8/7/14
to vcap...@cloudfoundry.org
Who is responsible for maintaining that service? Can someone verify that it's up right now?

No matter where I am when I make a call to that IP address, it fails. Most of the time it returns the Network Error HTML page that I pasted in my original message.

Daniel

Daniel Watrous

unread,
Aug 7, 2014, 3:34:35 PM8/7/14
to vcap...@cloudfoundry.org
It's also curious that cloudfoundry or openstack would have a single point of failure dependency on a service hosted at that specific IP address. What about private clouds that may not have access to the wider internet?


On Wednesday, August 6, 2014 6:30:21 PM UTC-5, Dies Koper wrote:

Daniel Watrous

unread,
Aug 7, 2014, 3:53:24 PM8/7/14
to vcap...@cloudfoundry.org
Here's a screenshot of me trying again. It always produces a 503 response:



On Wednesday, August 6, 2014 6:30:21 PM UTC-5, Dies Koper wrote:

Ferran Rodenas

unread,
Aug 7, 2014, 5:07:56 PM8/7/14
to vcap...@cloudfoundry.org
Daniel, that endpoint is not a public one, it's something internal to your OpenStack environment (AWS uses the same approach). 

When you deploy OpenStack, the compute/networking component starts a special metadata service that listens on port 80. When inside one of your virtual machines you try to access that address (169.254.169.254), OpenStack will redirect that call to the metadata service, and it will return only the specific data related to the virtual machine that made the query. 

So you need to run the curl command from inside one of your virtual machines. If the endpoint is not responding, that would mean that the metadata server has not been enabled in your OpenStack environment.

- Ferdy


To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/b3730165-8381-4fa1-9cc2-4c77a9f86f1a%40cloudfoundry.org.

Koper, Dies

unread,
Aug 7, 2014, 5:52:15 PM8/7/14
to vcap...@cloudfoundry.org

Hi Daniel,

 

If you are just checking the prerequisites for installing CF on OpenStack, I believe BOSH has a fallback method:

If the metadata service is not available it will try to inject a file into your VM with the parameters instead. So you could try proceeding to the next validation step and start the installation anyway.

Rackspace Public Cloud for example doesn’t support the metadata service.

 

Regards,

Dies Koper

Ferran Rodenas

unread,
Aug 7, 2014, 5:58:51 PM8/7/14
to vcap...@cloudfoundry.org
Unfortunately the fallback mechanism is not supported in the go agent, so you'll need to use an old stemcell with the ruby agent (2624 is the latest ruby one).

- Ferdy


To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/C3E9EF18297CC8438A31E391B8AFF674476A9E%40SYD1217.

Koper, Dies

unread,
Aug 7, 2014, 6:05:24 PM8/7/14
to vcap...@cloudfoundry.org

Hi Ferdy,

 

Good to know! Is that something that will be supported in the near future?

 

I’m thinking it may be worth sending in a PR to update the section in http://docs.cloudfoundry.org/deploying/openstack/validate_openstack.html#metadata_service

 

“you can also try inserting instance specific data such as injecting a file when booting a VM” - which will send the user on a wild goose hunt, installing fog etc. all to eventually fail at the final bosh deploy step.

 

Cheers,

Ferran Rodenas

unread,
Aug 7, 2014, 6:16:23 PM8/7/14
to vcap...@cloudfoundry.org
I don't know exactly what are the plans, but what I'm sure is that 'server personalities' (or injected user files) are not going to be supported anymore (they've been a source of problems at lots of environments). I know we talked about supporting 'config-drive', but not sure if and when will be supported.

For sure a PR removing that section of the docs will be greatly appreciated.

- Ferdy


To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/C3E9EF18297CC8438A31E391B8AFF674476B1F%40SYD1217.

hpdan...@gmail.com

unread,
Aug 25, 2014, 4:37:34 PM8/25/14
to vcap...@cloudfoundry.org
Thanks. I get it now. After reading the instructions more carefully I can see that it is intended to be executed from a VM.

It works as expected.
Reply all
Reply to author
Forward
0 new messages