Destroying role instances always leaves a VHD file behind

Bug #1216744 reported by Julian Edwards
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Go Windows Azure Client Library
Fix Released
Critical
Andrew Wilkins

Bug Description

In my storage account's 'vhds' container, I can see a 29.5GB file for every role instance (cloud service) I've ever launched. They are never cleaned up when gwacl destroys a virtual machine.

Related branches

Changed in gwacl:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Andrew Wilkins (axwalk) wrote :

"""
err = api.DeleteDisk(&DeleteDiskRequest{
    DiskName: diskName,
    DeleteBlob: false}) // change to true at some point?
"""

Is there a reason why that is false?

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 1216744] Re: Destroying role instances always leaves a VHD file behind

On 27/08/13 10:33, Andrew Wilkins wrote:
> """
> err = api.DeleteDisk(&DeleteDiskRequest{
> DiskName: diskName,
> DeleteBlob: false}) // change to true at some point?
> """
>
> Is there a reason why that is false?
>

I can't remember. I don't think there is any good reason.

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

Other bug subscribers

Remote bug watches

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