Project

General

Profile

Actions

Bug #1506

closed

failed to remove instance storage

Added by Adrian Bridgett about 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
VM management
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I created a pile of VMs (using hostgroups)

Upon deleting them, their storage volumes have been left around.

The hypervisor has two storage pools in this case (default and rootvg) and the volume resided in the rootvg pool.

production log shows:

Removing Libvirt instance for for bl-cassandra-s06.example.com
Removing Libvirt instance storage for bl-cassandra-s06.example.com
Delete DHCP reservation for bl-cassandra-s06.visualdna.com-52:54:00:f4:a0:91/10.200.10.66
Delete the TFTP configuration for bl-cassandra-s06.example.com
Remove puppet certificate for bl-cassandra-s06.example.com
Delete the autosign entry for bl-cassandra-s06.example.com
(no errors)

virsh c qemu+ssh://root@bl-vmhost-s02/system vol-list --pool rootvg
Name Path
----------------------------------------

bl-cassandra-s02.example.com.img /dev/rootvg/bl-cassandra-s02.example.com.img
bl-cassandra-s06.example.com.img /dev/rootvg/bl-cassandra-s06.example.com.img

virsh -c qemu+ssh://root@bl-vmhost-s02/system vol-delete bl-cassandra-s02.example.com.img
error: failed to get vol 'bl-cassandra-s02.visualdna.com.img'
error: Storage volume not found: no storage vol with matching path

virsh -c qemu+ssh://root@bl-vmhost-s02/system vol-delete bl-cassandra-s02.example.com.img --pool rootvg
Vol bl-cassandra-s02.visualdna.com.img deleted

Foreman 0.4.1

Actions

Also available in: Atom PDF