Ask Your Question

Windows 2008 64 images fail to get IP assigned when upgrading to Grizzly

asked 2013-05-12 22:53:03 -0600

Jcglobal gravatar image

updated 2013-05-13 12:37:22 -0600

smaffulli gravatar image

I'm migrating from essex to grizzly, i've copied my windows 2008 64 images which was fully functional and i did the import process sucessfull.

When a new instance it's provisioned with the migrated image the IP Assigment doesn't work on windows i mean the internal IP not a floating ip.

Somebody could help?


edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2013-05-15 00:58:03 -0600

Ankit gravatar image

updated 2013-05-15 01:04:08 -0600

Are you seeing duplicate ips or no ips assign in every next instances? What versions are you currently running in all components of Openstack - Grizzly? In between, try to give some time ( around 2-3 minutes) to fetch the ip from dhcp agent.

edit flag offensive delete link more

answered 2013-05-13 21:26:43 -0600

Jcglobal gravatar image

Just the first time the DHCP works after the second instance it's provisioned i get the following error on quantum server on controller node:

2013-05-13 11:57:51 WARNING [quantum.db.agentschedulersdb] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'72713569-7bac-4fe8-9966-69472fec56b2'], 'name': u'redoperacion', 'provider:physicalnetwork': None, 'adminstateup': True, 'tenantid': u'45107d29bf874007a75ebbd4b4b0438b', 'provider:networktype': u'gre', 'router:external': False, 'shared': False, 'id': u'13331fdb-8815-47af-b27e-9de3ef654d5f', 'provider:segmentationid': 1L}

BTW: The problem it's not just windows it's all the images even ubuntu.

Some clue?

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-05-12 22:53:03 -0600

Seen: 308 times

Last updated: May 15 '13