openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #22508
Re: vm unable to reach 169.254.169.254
Hi,
Are you using namespaces ? b/c i think this is related to
https://bugs.launchpad.net/quantum/+bug/1160955, if so a fix was just
commited in the stable grizzly branch, so upgrade if you want to use
another port than the default one, or i think removing the option metadata_port
from l3_agent.ini should also make it work for you.
HTH,
--
Mouad
On Tue, Apr 9, 2013 at 11:48 AM, Liu Wenmao <marvelliu@xxxxxxxxx> wrote:
> hi all:
>
> I setup quantum and nova grizzly, but vms can not get public key from
> 169.254.169.254:
>
>
> ############ debug end ##############
> cloudsetup: failed to read iid from metadata. tried 30
> WARN: /etc/rc3.d/S45cloudsetup failed
> Starting dropbear sshd: generating rsa key... generating dsa key... OK
> ===== cloudfinal: system completely up in 39.98 seconds ====
> wget: can't connect to remote host (169.254.169.254): Connection refused
> wget: can't connect to remote host (169.254.169.254): Connection refused
> wget: can't connect to remote host (169.254.169.254): Connection refused
> instanceid:
> publicipv4:
>
> I have configured nova.conf
> enabled_apis=ec2,osapi_compute,metadata
> metadata_manager=nova.api.manager.MetadataManager
> metadata_listen=0.0.0.0
> metadata_listen_port=8775
> service_quantum_metadata_proxy=true
> metadata_host=20.0.0.1
> metadata_port=8775
>
> quantum l3_agent.ini
> metadata_ip = 20.0.0.1
> metadata_port = 8775
>
> metadata_agent.ini
> nova_metadata_ip = 20.0.0.1
> nova_metadata_port = 8775
>
> 20.0.0.1 is my controller ip.
>
> p.s. I can not see any things like "169.254.169.254" in the iptables of
> controller or compute nodes.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References