New Question

Windows instances failed to setup network.

asked 2017-06-14 00:39:43 +0200

fishyu gravatar image


I am having some weird issue with creating Windows instances on OpenStack Ocata.

We are creating our instances in the external network, and used to work fine in Liberty.

The issue we are seeing is that about half of the instances fail to connect to Metadata server because the Cloudbase MTUPlugin doesn't set the MTU value to 1450(By comparing the cloudbase log between failed instances and functioning instances).

The Cloudbase version is 0.9.9, and we use openstack self-service network setup based on the Ocata doc.

Another weird thing we see is that creating instance is working under the same subnet where compute nodes and controller node stay, but about half instances malfunction if it's in a different subnet.

Consider we put all nodes in, VLAN is 10.10.136/22, and instances in, 10.10.138/24 and are having this issue.

edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted

answered 2017-06-14 00:42:05 +0200

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

Failed instances log:

edit flag offensive delete link more

answered 2017-06-14 14:24:46 +0200

avladu gravatar image


Can you share the two logs(cloudbase-init. log and cloudbase-init-unattend.log) for only one failed instance?
Please put the logs on a pastebin next time, as it is very hard to look at them otherwise.

This might be an issue with the dhcp service in Neutron. The instances that you spawn, also, have only one nic?

Thank you, Adrian Vladu

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

Question Tools


Asked: 2017-06-14 00:39:43 +0200

Seen: 72 times

Last updated: Jun 14 '17