Ask Your Question

Revision history [back]

After login to CirrOS instance try to run :-
$ curl http://169.254.169.254
$ ping 8.8.8.8
Does CirrOS instance complaining 169.254.169.254 when starting up ?

After login to CirrOS instance try to run :-
$ curl http://169.254.169.254
$ ping 8.8.8.8
Does CirrOS instance complaining 169.254.169.254 when starting up ?

image description

After login to CirrOS instance try to run :-
$ curl http://169.254.169.254
$ ping 8.8.8.8
Does CirrOS instance complaining 169.254.169.254 when starting up ?

image descriptionimage description

After login to CirrOS instance try to run :-
$ curl http://169.254.169.254
$ ping 8.8.8.8
Does CirrOS instance complaining 169.254.169.254 when starting up ?

image descriptionimage description

After login to CirrOS instance try to run :-
$ curl http://169.254.169.254
$ ping 8.8.8.8
Does CirrOS instance complaining 169.254.169.254 when starting up ?

image descriptionimage description

After login to CirrOS instance try to run :-
$ curl http://169.254.169.254http://169.254.169.254/latest/meta-data
$ ping 8.8.8.8
Does CirrOS instance complaining 169.254.169.254 when starting up ?

image description

After login to CirrOS instance try to run :-
$ curl http://169.254.169.254/latest/meta-data
$ ping 8.8.8.8
Does CirrOS instance complaining 169.254.169.254 when starting up ?

image description

Failure  to run   
$ curl http://169.254.169.254/latest/meta-data/instance-id 
$ curl http://169.254.169.254/latest/meta-data/ 
is a core reason of your problems. You don't have access to nova metadata server, 
what causes cloud-init to fail setting up your CirrOS instance.
View troubleshooting steps here  http://bderzhavets.blogspot.com/2014/07/rdo-setup-two-real-node.html