Also this is even after waiting for the main expunge thread to run. The volumes remain non-removed after the expunger runs.
On Wed, Jan 27, 2016 at 1:56 PM, Jeff Hair <j...@greenqloud.com> wrote: > Hi, > > In a 4.2 environment, after removing the last host from a zone and > destroying the system VMs, they leave behind their volume in the database > stuck in Expunging, but the removed column is non-NULL. This prevents the > deletion of the primary storage. Was this fixed in later versions or does > it still happen? > > Thanks, > > Jeff > -- *Jeff Hair* Technical Lead and Software Developer Tel: (+354) 415 0200 j...@greenqloud.com www.greenqloud.com
