Public bug reported: I am running OpenStack Mitaka on CentOS7.1 with Citrix XenServer 6.5 Standard Edition. My XenServer host has been installed following software updates: XS65ESP1,XS65ESP1013 and XS65ESP1021. I Use Cloud-init to customize OpenStack instances by enabling force_config_drive configuration item. For CentOS and Ubuntu OS., Cloud-init works well, which can customize hostname, password and network address properly, but for windows OS.,Cloudbase-init works badly.
I generate Windows Server 2012 R2 image according to this blog (url: https://www.citrix.com/blogs/2016/09/08/generating-images-for-xenserver-in-openstack/). Cloudbase-init version 0.9.9. Instance name in OpenStack is aaa2 and it's name in XenServer is aaa2-1. Taking a look on XenCenter connected to my XenServer, seems like config-2 vfat disk is working fine, this is a print screen: |---------------------------------------------------------------------------------------------------------------------------- |Position Name Description SR Size Read Only Priority Active Device Path |0 aaa2-1 root Local storage on xenserver 40G No 0(Lowest) Yes /dev/xvda |3 config-2 configdrive Local storage on xenserver 64M Yes 0(Lowest) Yes /dev/xvdd |---------------------------------------------------------------------------------------------------------------------------- But, I need reset administrator's password when login this instance( Windows prompts the user's password must be changed before signing in). After reseting password and logon, I find hostname and network address have not been customized according to the instance metadata. In Disk Management of Server Manager, vfat disk has not been listed. Cloudbase-init log file contains this: ........ 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive vfat in partition get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive vfat in cdrom get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Irrelevant type vfat in cdrom location; get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:195 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive vfat in hdd get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.utils.windows.vfat [-] Could not retrieve label for VFAT drive path '\\\\.\\PHYSICALDRIVE0' is_vfat_drive c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\windows\vfat.py:53 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.utils.windows.vfat [-] mlabel failed with error b"init :: sector size (190) not a small power of two\r\nCannot initalize '::'\r\nC:\\Program Files\\Cloudbase Solutions\\Cloudbase-Init\\bin\\mlabel: Cannot initialize drive\r\n" is_vfat_drive c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\windows\vfat.py:54 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive iso in partition get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 ........ I checked the cloudbase-init configuration item carefully and found no errors. I have read several posts, they all don't mention above problem. Thanks in advance for your help. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1686056 Title: xenserver windows instance customize failed by cloudbase-init Status in OpenStack Compute (nova): New Bug description: I am running OpenStack Mitaka on CentOS7.1 with Citrix XenServer 6.5 Standard Edition. My XenServer host has been installed following software updates: XS65ESP1,XS65ESP1013 and XS65ESP1021. I Use Cloud- init to customize OpenStack instances by enabling force_config_drive configuration item. For CentOS and Ubuntu OS., Cloud-init works well, which can customize hostname, password and network address properly, but for windows OS.,Cloudbase-init works badly. I generate Windows Server 2012 R2 image according to this blog (url: https://www.citrix.com/blogs/2016/09/08/generating-images-for-xenserver-in-openstack/). Cloudbase-init version 0.9.9. Instance name in OpenStack is aaa2 and it's name in XenServer is aaa2-1. Taking a look on XenCenter connected to my XenServer, seems like config-2 vfat disk is working fine, this is a print screen: |---------------------------------------------------------------------------------------------------------------------------- |Position Name Description SR Size Read Only Priority Active Device Path |0 aaa2-1 root Local storage on xenserver 40G No 0(Lowest) Yes /dev/xvda |3 config-2 configdrive Local storage on xenserver 64M Yes 0(Lowest) Yes /dev/xvdd |---------------------------------------------------------------------------------------------------------------------------- But, I need reset administrator's password when login this instance( Windows prompts the user's password must be changed before signing in). After reseting password and logon, I find hostname and network address have not been customized according to the instance metadata. In Disk Management of Server Manager, vfat disk has not been listed. Cloudbase-init log file contains this: ........ 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive vfat in partition get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive vfat in cdrom get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Irrelevant type vfat in cdrom location; get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:195 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive vfat in hdd get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.utils.windows.vfat [-] Could not retrieve label for VFAT drive path '\\\\.\\PHYSICALDRIVE0' is_vfat_drive c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\windows\vfat.py:53 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.utils.windows.vfat [-] mlabel failed with error b"init :: sector size (190) not a small power of two\r\nCannot initalize '::'\r\nC:\\Program Files\\Cloudbase Solutions\\Cloudbase-Init\\bin\\mlabel: Cannot initialize drive\r\n" is_vfat_drive c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\windows\vfat.py:54 2017-04-08 03:49:05.560 1696 DEBUG cloudbaseinit.metadata.services.osconfigdrive.windows [-] Looking for Config Drive iso in partition get_config_drive_files c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:206 ........ I checked the cloudbase-init configuration item carefully and found no errors. I have read several posts, they all don't mention above problem. Thanks in advance for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1686056/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp