Revision history [back]

Hello,

We are doing many tests on WS2012 R2 (W8 X64) and we couldn't observe such behavior (on VMWare and on OpenStack (with devstack)). If the DHCP is disabled (through the custom IP and broadcast addresses which are set first), then there should be no problem for "ready" state of the NIC when setting DNSes. Also, there is no default validation (ping/request) for the custom addresses (only basic checks) from the OS API when setting them, so you don't have to worry if that DNS address is valid and reachable in that particular moment.

One solution for the moment is to:

1. Provide additional and extensive information regarding the environment you are currently using for your windows image and a full cloudbase-init log. (infrastructure, type of deployment, versions, configuration files, config drive content)

2. Make some tests until the error is reproduced using the beta installer found here: https://www.cloudbase.it/downloads/CloudbaseInitSetup_x64.msi with this patch applied: https://review.openstack.org/#/c/219305/ if it's not present there yet (because it may take a little time for the merge and the lastest build) and you should see in the logs the error code for which the DNS setting has failed.

Hello,

We are doing many tests on WS2012 R2 (W8 X64) and we couldn't observe such behavior (on VMWare and on OpenStack (with devstack)). If the DHCP is disabled (through the custom IP and broadcast addresses which are set first), then there should be no problem for "ready" state of the NIC when setting DNSes. Also, there is no default validation (ping/request) for the custom addresses (only basic checks) from the OS API when setting them, so you don't have to worry if that DNS address is valid and reachable in that particular moment.

One solution for the moment is to:

1. Provide additional and extensive information regarding the environment you are currently using for your windows image and a full cloudbase-init log. (infrastructure, type of deployment, versions, configuration files, config drive content)metadata content etc.)

2. Make some tests until the error is reproduced using the beta installer found here: https://www.cloudbase.it/downloads/CloudbaseInitSetup_x64.msi with this patch applied: https://review.openstack.org/#/c/219305/ if it's not present there yet (because it may take a little time for the merge and the lastest build) and you should see in the logs the error code for which the DNS setting has failed.