juju-core

juju/azure doesn't cleanup its private containers

Bug #1324599 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Medium
Andrew Wilkins
juju-core 1.19.4

Bug Description

several azure tests were failing in Juju CI. We suspected that the private container might contain cruft from previous tests. I looked. There was a container for each env CI had ever used left behind. BUT OMG. The storage container has 366 vhds, each one is 29.4G. I think that is 10.7T of images juju/azure left behind in our tests from the last 9 months.

Revision history for this message
Curtis Hovey (sinzui) wrote :

There are no machines. I manually deleted all services, machines, and networks left behind by juju or azure. But I cannot delete the vhds:

The following virtual machine disks are currently using blobs in this container, so the container cannot be deleted: juju-azure-deploy-hht58gr4bq-juju9jy2rxmuxxnam12gl9g2whjsnkog2ylgh8e7b2rgtt6kiq-0-201404291850020846, juju-azure-upgrade-trusty-amd64-t4jzgqaeya-jujuewx87to7s8b2uu89n69vs1br0y5gswb04lxz0pnexinoxp-0-201405291531270643, juju-test-azure-654hotdhmv-jujuc9iynob5fxpc4ncawx8sd63x9zvgk0l6ks4v1quv1lciza-0-201401281807100178, juju-test-azure-692qe65bjg-jujuy29xtnn145tynusqcdimzbeustf179ug206hlnrbrl74f6-0-201312021902360295, juju-test-azure-b89vdkgp4v-juju02ox45xx3c9kse8rjausr2yqrqsl46bd4i3iak4kcqohu5-0-201401302239540055, 469 more.

I repeat, there are no machines.

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1324599] Re: juju/azure doesn't cleanup its private containers

Well, there is a "virtual machine disk" that is apparently still up, even
though there isn't a machine that is using it.
John
=:->

On Thu, May 29, 2014 at 8:14 PM, Curtis Hovey <email address hidden> wrote:

> There are no machines. I manually deleted all services, machines, and
> networks left behind by juju or azure. But I cannot delete the vhds:
>
> The following virtual machine disks are currently using blobs in this
> container, so the container cannot be deleted: juju-azure-deploy-
> hht58gr4bq-
> juju9jy2rxmuxxnam12gl9g2whjsnkog2ylgh8e7b2rgtt6kiq-0-201404291850020846,
> juju-azure-upgrade-trusty-amd64-t4jzgqaeya-
> jujuewx87to7s8b2uu89n69vs1br0y5gswb04lxz0pnexinoxp-0-201405291531270643,
> juju-test-azure-654hotdhmv-
> jujuc9iynob5fxpc4ncawx8sd63x9zvgk0l6ks4v1quv1lciza-0-201401281807100178,
> juju-test-azure-692qe65bjg-
> jujuy29xtnn145tynusqcdimzbeustf179ug206hlnrbrl74f6-0-201312021902360295,
> juju-test-azure-b89vdkgp4v-
> juju02ox45xx3c9kse8rjausr2yqrqsl46bd4i3iak4kcqohu5-0-201401302239540055,
> 469 more.
>
> I repeat, there are no machines.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1324599
>
> Title:
> juju/azure doesn't cleanup its private containers
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1324599/+subscriptions
>

Revision history for this message
Andrew Wilkins (axwalk) wrote :

This was resolved when the availability set changes were made.

Changed in juju-core:
status: Triaged → Fix Committed
milestone: none → 1.19.4
assignee: nobody → Andrew Wilkins (axwalk)
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.