I have some OpenStack instances using a Windows Server 2016 image that are not extending their volumes to the max size of the disk, in this case 200GB. They are running Cloudbase-Init version: 0.9.9 this is what I'm seeing in the logs:
2016-10-26 13:26:35.083 2060 INFO cloudbaseinit.init [-] Executing plugin 'ExtendVolumesPlugin' 2016-10-26 13:26:35.098 2060 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.osutils.windows.WindowsUtils' loadclass c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2016-10-26 13:26:35.114 2060 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.utils.windows.storage.wsmstoragemanager.WSMStorageManager' loadclass c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2016-10-26 13:26:40.395 2060 INFO cloudbaseinit.utils.windows.storage.wsmstoragemanager [-] Extending partition "2" to 85372960768 bytes
Im not sure if its an issue with our image or this version of cloudbase-init, we do have another Windows Server 2016 image that has Cloudbase-Init version: 0.9.11 and its not having the same issue.
