[ovirt-users] Re: ILLEGAL volume delete via vdsm-client
On Wed, Nov 17, 2021 at 12:14 PM Francesco Lorenzini
<francesco(a)shellrent.com> wrote:
It worked now, my bad.
I mistakenly thought that the Storage Pool ID was the ID of the SPM Host and not the one
listed under /rhev/data-center/.
I used the correct SPUUID and everything worked correctly:
vdsm-client Volume delete storagepoolID=609ff8db-09c5-435b-b2e5-023d57003138
volumeID=5cb3fe58-3e01-4d32-bc7c-5907a4f858a8
storagedomainID=e25db7d0-060a-4046-94b5-235f38097cd8 imageID=4d
79c1da-34f0-44e3-8b92-c4bcb8524d83 force=true postZero=False
"d85d0a83-fec0-4472-87fd-e61c8c3e0608"
Removed the task ID d85d0a83-fec0-4472-87fd-e61c8c3e0608 by vdsm-client Task clear
taskID=d85d0a83-fec0-4472-87fd-e61c8c3e0608
Sorry for the waste of time and thank you.
No problem, we are happy to help.
I think the error message could easily be improved - this is the relevant code:
@classmethod
def getPool(cls, spUUID):
if cls._pool.is_connected() and cls._pool.spUUID == spUUID:
return cls._pool
# Calling when pool is not connected or with wrong pool id is client
# error.
raise exception.expected(se.StoragePoolUnknown(spUUID))
We should really report different errors for unconnected pool and
incorrect pool id,
for example:
Incorrect pool id 'c0e7a0c5-8048-4f30-af08-cbd17d797e3b', connected to
pool '609ff8db-09c5-435b-b2e5-023d57003138'
If you think this is useful please file a bug to improve this.
Nir