Foreman 1.4.1: GCE Compute Resource Instances leave disks when deleted (Orphaned Disks)

Is it expected behaviour that when you delete an GCE instance using foreman
that the disk remains on GCE?

The cost of the orphaned disk which might not break the bank but from an
administration point of view it leaves alot of unattached disks in a
project with no easy way to tell if they were meant to be kept or left over
when the instance was deleted

Maybe foreman should ask if the user wants to delete the boot disk like
cloud console currently does or is this to avoid the situation of other
attached disks being deleted as well?

··· On Tuesday, February 25, 2014 11:19:10 AM UTC, michael...@ul.ie wrote: > > Is it expected behaviour that when you delete an GCE instance using > foreman that the disk remains on GCE? > > The cost of the orphaned disk which might not break the bank but from an > administration point of view it leaves alot of unattached disks in a > project with no easy way to tell if they were meant to be kept or left over > when the instance was deleted >

Generally compute resources in Foreman should delete disks when the host
is deleted. So without any knowledge of GCE, I'd say this is what it
should be doing too and that's a bug.

We avoid interactive questions on deletion (and have a similar question
with libvirt open at the moment for volumes that can't be deleted, e.g.
block devices) because we don't have API or CLI equivalents.

··· On 25/02/14 11:19, michael.obrien@ul.ie wrote: > Is it expected behaviour that when you delete an GCE instance using > foreman that the disk remains on GCE? > > The cost of the orphaned disk which might not break the bank but from an > administration point of view it leaves alot of unattached disks in a > project with no easy way to tell if they were meant to be kept or left > over when the instance was deleted


Dominic Cleal
Red Hat Engineering