On Wed, Nov 17, 2021 at 12:14 PM Francesco Lorenzini
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
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
On Wed, Nov 17, 2021 at 10:32 AM Francesco Lorenzini <
france...@shellrent.com> wrote:
> Hi Nir,
>
> sadly in the vdsm log there aren't more useful info:
>
> 2021-11-17 09:27:59,419+0100 INFO (Reactor thread)
> [ProtocolDetector.AcceptorImpl] Accepted connection from ::1:56392
>
Hi Nir,
sadly in the vdsm log there aren't more useful info:
2021-11-17 09:27:59,419+0100 INFO (Reactor thread)
[ProtocolDetector.AcceptorImpl] Accepted connection from ::1:56392
(protocoldetector:61)
2021-11-17 09:27:59,426+0100 WARN (Reactor thread) [vds.dispatcher]
unhandled write event
On Tue, Nov 16, 2021 at 4:07 PM francesco--- via Users wrote:
>
> Hi all,
>
> I'm trying to delete via vdsm-client toolan illegal volume that is not listed
> in the engine database. The volume ID is 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8:
>
> [root@ovirthost ~]# vdsm-tool dump-volume-chains
>
5 matches
Mail list logo