Hello Fellows, Just to elaborate on Piyush’s ask, cloudstack user has got a new feature added where while creating independent cloudstack-volume, user would get ‘create on storage’ toggle appearing on the UI.
If toggle is enabled then cloudstack calls for createAsync workflow immediately and desired objects would be created on the underneath storage and state of volume would appear as ready in CS UI. If toggle is disabled then CS only creates metadata in the CS DB, no call goes to underneath storage. And volume state would appear as allocated. And while attach workflow on this volume, call would go to storage and it would create desired objects on the storage. Framework code is added in the VolumeServiceImpl class for this toggle. Query is, while this toggle is enabled, format for the disk is expected to be set as per chosen hypervisor. In absense of this format, subsequent workflow of snapshot is found to be failed. We propose to set this format in VolumeServiceImpl itself by which all the vendors will get benefit of it. Or we can add this setter for format in our driver class for creAsync method. Can you share you thoughts on this soon since it is important to go in 4.23 else multiple customers may get impacted in snapshot workflows. Regards Rajiv Jain On Fri, 17 Jul 2026 at 7:59 PM, Piyush Srivastava < [email protected]> wrote: > Hi Team, > > I was using the "Create on Storage" option in Create Volume wizard for > creating and attaching the volume to a particular instance. > I can see the volume is created as well as attached to the instance. > But when I cross checked the db for the format set for this volume , I see > it as "NULL" rather than actual format . > Is there any issue seen due to this null format set? > > [image: image.png] > mysql> select name,format from volumes where name="testAttach1"; > +-------------+--------+ > | name | format | > +-------------+--------+ > | testAttach1 | NULL > > I have observed the issue while creating a snapshot for that volume. Checking > here for blast radius of the issue before raising a PR and if it is > critical for 4.23.0. > > Thanks, > Piyush >
