Ask Your Question
3

Windows instance can not reach metadata?

asked 2013-10-07 09:57:15 -0500

n-paladi gravatar image

updated 2013-10-11 18:05:50 -0500

smaffulli gravatar image

I am using a CentOS-based OpenStack deployment and am running both Linux and Windows instances. I've used the installer from CloudBase for the Windows instances (Win 7 and Win Server 2012).

However, when booting up, the windows instances can not reach the metadata (identical log as specified by user "George", December 19, 2012 at 7:21 on http://www.cloudbase.it/cloud-init-for-windows-instances/ )

Important to note is that the linux test instances DO get access to the metadata in the same deployment.

edit retag flag offensive close merge delete

Comments

darragh-oreilly gravatar imagedarragh-oreilly ( 2013-10-07 10:10:39 -0500 )edit

they are Win 7 and Win Server 2012

n-paladi gravatar imagen-paladi ( 2013-10-07 10:12:09 -0500 )edit

pasting your logs in the question would make yours more easy to parse

smaffulli gravatar imagesmaffulli ( 2013-10-11 18:06:43 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2019-01-06 17:17:51 -0500

tze gravatar image

Because you say the Linux vms can access the the metadata service i think the installations of openstack (nova, neutron, etc) works fine. Is your windows instance has network adapter correct drivers? More simple, has your instance access to network or only console you can get? Depend of attributes in image you use the nova use different network adapter emulation. So check that your net is ok. Second think is the adapter to be configured as dhcp configuration because openstack send custom routes for ip 169.254.169.254 if you use provider networks (this is not the case in tenant networks with l3 agent). Check your route with command route print on a terminal. if your metadata service works you must get correct response for url http://169.254.169.254/.

edit flag offensive delete link more
0

answered 2019-01-02 11:39:06 -0500

BiG_NoBoDy gravatar image

1) Create VM with config drive.

2) if 1st does not work, check "netstat -rn" (it should be able to reach/added 169.254.254.254 ?? I do not remember IP address by heart).

edit flag offensive delete link more

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

Stats

Asked: 2013-10-07 09:57:15 -0500

Seen: 527 times

Last updated: Jan 06