Ask Your Question
0

tripleo queens metadata 404

asked 2019-10-11 23:49:57 -0500

jkrah gravatar image

updated 2019-10-12 01:46:00 -0500

Hi guys, been playing around with tripleo-queens and really happy to get a single controller cloud running with network isolation.

But when I try to build a 3 controller cloud (with rendered/environments/docker-ha.yaml) I'm getting a strange behavior from the (distributed) metadata agent..

From what I can tell there seem to be multiple requests for "/2009-04-04/user-data" , one which gets a 404 .. the other gets a 200

Servers (instances) boot but fail to get metadata ..

 Failed fetching metadata from url http://169.254.169.254/2009-04-04/meta-data

Any clues on how to debug ? thank heaps :-)

(tcpdump -v)

GET /2009-04-04/user-data HTTP/1.1
Host: 169.254.169.254
Connection: keep-alive
Accept-Encoding: gzip, deflate
Accept: */*
User-Agent: Cloud-Init/0.7.5

(5 secsonds later)

GET /2009-04-04/meta-data HTTP/1.1
Host: 169.254.169.254
Connection: keep-alive
Accept-Encoding: gzip, deflate
Accept: */*
User-Agent: Cloud-Init/0.7.5

Then in response..

HTTP/1.1 404 Not Found
Content-Length: 154
Content-Type: text/html; charset=UTF-8
Date: Sat, 12 Oct 2019 04:31:00 GMT

<html>
 <head>
  <title>404 Not Found</title>
 </head>
 <body>
  <h1>404 Not Found</h1>
  The resource could not be found.<br /><br />
...

(and)

HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Content-Length: 223
Date: Sat, 12 Oct 2019 04:31:04 GMT

ami-id
ami-launch-index
ami-manifest-path
block-device-mapping/
hostname
instance-action
instance-id
instance-type
local-hostname
local-ipv4
placement/
public-hostname
public-ipv4
public-keys/
reservation-id
security-groups[!http]
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-10-12 01:15:48 -0500

jkrah gravatar image

Looks like IPTables was blocking memcached on my controller nodes.. I added this to each controller node and metadata is now working again.. (vlan13 is my InternalApi network) ..

iptables -I INPUT 5  -i vlan13 -p tcp --dport 11211 -j ACCEPT  -m state --state NEW -m comment --comment "added memcached"

I will leave this here in case this info helps anyone else out or if anyone can suggest a better fix..

edit flag offensive delete link more

Comments

jkrah gravatar imagejkrah ( 2019-10-12 01:48:43 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-10-11 23:49:57 -0500

Seen: 6 times

Last updated: Oct 12