New Question
0

Windows Server 2016 volume resize issues

asked 2018-06-26 02:26:35 +0200

sruzgar gravatar image

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.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2018-07-09 19:33:21 +0200

avladu gravatar image

Hello,

I think you have hit a known fixed bug: https://github.com/openstack/cloudbas...

Please use the latest cloudbase-init version.

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

Stats

Asked: 2018-06-26 02:26:35 +0200

Seen: 47 times

Last updated: Jul 09