Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Unable to connect to neutron metadata

# ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea curl -I http://169.254.169.254/2009-04-04/meta-data/instance-id curl: (7) Failed connect to 169.254.169.254:80; Connection refused

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea ping 169.254.169.254

PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.040 ms 64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.030 ms 64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.031 ms 64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.028 ms

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -anpe

Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 10.10.0.2:53 0.0.0.0:* LISTEN 0 257683 9023/dnsmasq
tcp 0 0 169.254.169.254:53 0.0.0.0:* LISTEN 0 257681 9023/dnsmasq
tcp6 0 0 fe80::f816:3eff:fe8a:53 :::* LISTEN 0 257685 9023/dnsmasq
udp 0 0 10.10.0.2:53 0.0.0.0:* 0 257682 9023/dnsmasq
udp 0 0 169.254.169.254:53 0.0.0.0:* 0 257680 9023/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 0 257673 9023/dnsmasq
udp6 0 0 fe80::f816:3eff:fe8a:53 :::* 0 257684 9023/dnsmasq

http://kimizhang.com/metadata-service-in-dhcp-namespace/ as per this blog I can see 80 port in my name space is missing

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -nltp | grep :80

I have 2 network nodes. VMs created before are working fine but when try to create new VMs facing this issue.

Unable to connect to neutron metadata

#

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea curl -I http://169.254.169.254/2009-04-04/meta-data/instance-id http://169.254.169.254/2009-04-04/meta-data/instance-id

curl: (7) Failed connect to 169.254.169.254:80; Connection refused

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea ping 169.254.169.254

PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.040 ms 64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.030 ms 64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.031 ms 64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.028 ms

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -anpe

Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 10.10.0.2:53 0.0.0.0:* LISTEN 0 257683 9023/dnsmasq
tcp 0 0 169.254.169.254:53 0.0.0.0:* LISTEN 0 257681 9023/dnsmasq
tcp6 0 0 fe80::f816:3eff:fe8a:53 :::* LISTEN 0 257685 9023/dnsmasq
udp 0 0 10.10.0.2:53 0.0.0.0:* 0 257682 9023/dnsmasq
udp 0 0 169.254.169.254:53 0.0.0.0:* 0 257680 9023/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 0 257673 9023/dnsmasq
udp6 0 0 fe80::f816:3eff:fe8a:53 :::* 0 257684 9023/dnsmasq

http://kimizhang.com/metadata-service-in-dhcp-namespace/ as per this blog I can see 80 port in my name space is missing

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -nltp | grep :80

I have 2 network nodes. VMs created before are working fine but when try to create new VMs facing this issue.

Unable to connect to neutron metadata

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea curl -I http://169.254.169.254/2009-04-04/meta-data/instance-id

curl: (7) Failed connect to 169.254.169.254:80; Connection refused

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea ping 169.254.169.254

PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.040 ms 64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.030 ms 64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.031 ms 64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.028 ms

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -anpe

Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 10.10.0.2:53 0.0.0.0:* LISTEN 0 257683 9023/dnsmasq
tcp 0 0 169.254.169.254:53 0.0.0.0:* LISTEN 0 257681 9023/dnsmasq
tcp6 0 0 fe80::f816:3eff:fe8a:53 :::* LISTEN 0 257685 9023/dnsmasq
udp 0 0 10.10.0.2:53 0.0.0.0:* 0 257682 9023/dnsmasq
udp 0 0 169.254.169.254:53 0.0.0.0:* 0 257680 9023/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 0 257673 9023/dnsmasq
udp6 0 0 fe80::f816:3eff:fe8a:53 :::* 0 257684 9023/dnsmasq

http://kimizhang.com/metadata-service-in-dhcp-namespace/ as per this blog I can see 80 port in my name space is missing

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -nltp | grep :80

I have 2 network nodes. VMs created before are working fine but when try to create new VMs facing this issue.

Instance console log about the failure of metadata:

Unable to connect to neutron metadata

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea curl -I http://169.254.169.254/2009-04-04/meta-data/instance-id

curl: (7) Failed connect to 169.254.169.254:80; Connection refused

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea ping 169.254.169.254

PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.040 ms 64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.030 ms 64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.031 ms 64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.028 ms

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -anpe

Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 10.10.0.2:53 0.0.0.0:* LISTEN 0 257683 9023/dnsmasq
tcp 0 0 169.254.169.254:53 0.0.0.0:* LISTEN 0 257681 9023/dnsmasq
tcp6 0 0 fe80::f816:3eff:fe8a:53 :::* LISTEN 0 257685 9023/dnsmasq
udp 0 0 10.10.0.2:53 0.0.0.0:* 0 257682 9023/dnsmasq
udp 0 0 169.254.169.254:53 0.0.0.0:* 0 257680 9023/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 0 257673 9023/dnsmasq
udp6 0 0 fe80::f816:3eff:fe8a:53 :::* 0 257684 9023/dnsmasq

http://kimizhang.com/metadata-service-in-dhcp-namespace/ as per this blog I can see 80 port in my name space is missing

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -nltp | grep :80

I have 2 network nodes. VMs created before are working fine but when try to create new VMs facing this issue.

Instance console log about the failure of metadata:

Unable to connect to neutron metadata

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea curl -I http://169.254.169.254/2009-04-04/meta-data/instance-id

curl: (7) Failed connect to 169.254.169.254:80; Connection refused

refused # ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea ping 169.254.169.254

169.254.169.254 PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.040 ms 64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.030 ms 64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.031 ms 64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.028 ms

ms # ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -anpe

-anpe Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 10.10.0.2:53 0.0.0.0:* LISTEN 0 257683 9023/dnsmasq
tcp 0 0 169.254.169.254:53 0.0.0.0:* LISTEN 0 257681 9023/dnsmasq
tcp6 0 0 fe80::f816:3eff:fe8a:53 :::* LISTEN 0 257685 9023/dnsmasq
udp 0 0 10.10.0.2:53 0.0.0.0:* 0 257682 9023/dnsmasq
udp 0 0 169.254.169.254:53 0.0.0.0:* 0 257680 9023/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 0 257673 9023/dnsmasq
udp6 0 0 fe80::f816:3eff:fe8a:53 :::* 0 257684 9023/dnsmasq

9023/dnsmasq

http://kimizhang.com/metadata-service-in-dhcp-namespace/ as per this blog I can see 80 port in my name space is missing

# ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -nltp | grep :80

:80

I have 2 network nodes. VMs created before are working fine but when try to create new VMs facing this issue.

Instance console log about the failure of metadata:

Unable to connect to neutron metadata

ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea curl -I http://169.254.169.254/2009-04-04/meta-data/instance-id

curl: (7) Failed connect to 169.254.169.254:80; Connection refused

# ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea ping 169.254.169.254
PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data.
64 bytes from 169.254.169.254: icmp_seq=1 ttl=64 time=0.040 ms
64 bytes from 169.254.169.254: icmp_seq=2 ttl=64 time=0.030 ms
64 bytes from 169.254.169.254: icmp_seq=3 ttl=64 time=0.031 ms
64 bytes from 169.254.169.254: icmp_seq=4 ttl=64 time=0.028 ms

# ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -anpe
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name   
tcp        0      0 10.10.0.2:53            0.0.0.0:*               LISTEN      0          257683     9023/dnsmasq       
tcp        0      0 169.254.169.254:53      0.0.0.0:*               LISTEN      0          257681     9023/dnsmasq       
tcp6       0      0 fe80::f816:3eff:fe8a:53 :::*                    LISTEN      0          257685     9023/dnsmasq       
udp        0      0 10.10.0.2:53            0.0.0.0:*                           0          257682     9023/dnsmasq       
udp        0      0 169.254.169.254:53      0.0.0.0:*                           0          257680     9023/dnsmasq       
udp        0      0 0.0.0.0:67              0.0.0.0:*                           0          257673     9023/dnsmasq       
udp6       0      0 fe80::f816:3eff:fe8a:53 :::*                                0          257684     9023/dnsmasq

http://kimizhang.com/metadata-service-in-dhcp-namespace/ as per this blog I can see 80 port in my name space is missing

# ip netns exec qdhcp-fdad0564-091f-462d-81aa-32a46e3690ea netstat -nltp | grep :80

I have 2 network nodes. VMs created before are working fine but when try to create new VMs facing this issue.

Instance console log about the failure of metadata: