OpenStack Compute (nova)

VM can't talk to metadata service in multi-node install

Asked by Joseph Heck

Nova compute node is trying to access the metadata service on 169.254.169.254, and is unable to get there. It's a mutinode installation, and the node is receiving "connection refused", but the metadata service appears to be running.

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Joseph Heck
Solved:
Last query:
Last reply:
Revision history for this message
Joseph Heck (heckj) said : 		#1

The VM calls out to 168.254.169.254 for meta data. The nova-api service is ready to answer, but it only talks on :8773. It is nova-network's job to set up a NAT in its iptables to route all 169.254.169.254 traffic to the nova-api instance. My nova-network was sending the traffic to itself and not to the nova-api machine.

The correct flag to use is to set --ec2_dmz_host to the address of the nova-api service, otherwise it defaults to the address of the nova-network machine.

Revision history for this message
Joseph Heck (heckj) said : 		#2

The VM calls out to 168.254.169.254 for meta data. The nova-api service is ready to answer, but it only talks on :8773. It is nova-network's job to set up a NAT in its iptables to route all 169.254.169.254 traffic to the nova-api instance. My nova-network was sending the traffic to itself and not to the nova-api machine.

The correct flag to use is to set --ec2_dmz_host to the address of the nova-api service, otherwise it defaults to the address of the nova-network machine.

Revision history for this message
Joseph Heck (heckj) said : 		#3

Oops - correct IP address that it calls out to is: 169.254.169.254