Hi Piyush, If Netapp storage pool has the hypervisor set, this can be easily done from the driver. The change will be contained and low risk. 4.23 is already in RC1 testing phase - you might want to talk to the RMs if you want to get this included.
Some storage pools might have the HypervisorType as Any. A generic fix in volumeApiServiceImpl might not work or would need some testing. "What’s the format that the volume is created on disk with?” I meant what’s the filetype format of the volume file on storage - does qemu-img info give QCOW2 or RAW. Thanks, Abhisar From: Piyush Srivastava <[email protected]> Date: Monday, 20 July 2026 at 4:16 PM To: [email protected] <[email protected]> Cc: [email protected] <[email protected]>, PMC <[email protected]> Subject: Re: Issue in Create volume on specified storage Hi Abhisar, Yes it is observed on KVM and the issue does not only affect Netapp Plugin. Actually when storageId is passed as part of CreateVolumeCmd, createVolumeOnStoragePool does not set format of volume irrespective of pool type or hypervisor, whereas when createVolumeOnPrimaryStorage is called in attach workflow , it sets the volume format explicitly. For NFS it is working fine because CreateObjectAnswer sets the format internally. For others(like iSCSI etc), we should explicitly set the format same as createVolumeOnPrimaryStorage is doing currently. Also please find my answer for your questions: "What’s the format that the volume is created on disk with?" -> *NULL* if create on storage is used , *QCOW2* when create on storage toggle is not used. "What is the value of storage_pool.hypervisor in the DB for the Netapp storage pool?"-> KVM Thanks, Piyush On Mon, Jul 20, 2026, 11:47 AM Abhisar Sinha <[email protected]> wrote: > Hi Rajiv, > > Is this on KVM? > What’s the format that the volume is created on disk with? > I assume this is with the NetApp primary storage plugin. I checked that > the format is being set correctly on NFS storage. > What is the value of storage_pool.hypervisor in the DB for the Netapp > storage pool? > > Thanks, > Abhisar > > <https://www.cloudstackcollab.org> > *From: *Rajiv Jain <[email protected]> > *Date: *Monday, 20 July 2026 at 10:45 AM > *To: *[email protected] <[email protected]>, users < > [email protected]>, PMC <[email protected]> > *Subject: *Re: Issue in Create volume on specified storage > > Adding another PDL for visibility. > > Regards > Rajiv Jain > > On Sat, Jul 18, 2026 at 11:33 AM Rajiv Jain < > [email protected]> wrote: > > > 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 > >> > > >
