Provide developers with a "nuke it from orbit" option for cleaning up LXC

Bug #1312201 reported by Michael Hall
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

Test deploying to local LXC containers with Juju is a great way to rapidly iterate your charm development, but I find myself with broken LXC setup a *lot*, either through my own fault or because of an unexpected shutdown of my laptop. Either way I'm left with running container that Juju no longer recognizes, and juju services that the CLI tools can't connect to.

Since this is for local testing of my charm, it would be easier to just get rid of everything and start over from scratch. There's an AskUbuntu answer detailing how to do this[1] but it would be even better if there was a local tool (juju-scrub-local or something like that) which would forcibly clean up everything and put the local host back to a clean state ready to juju bootstrap again.

[1] http://askubuntu.com/questions/403618/how-do-i-clean-up-a-machine-after-using-the-local-provider

Tags: feature
Jorge Castro (jorge)
Changed in juju-core:
status: New → Confirmed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Confirmed → Triaged
importance: Undecided → Low
tags: added: feature
Revision history for this message
Dimiter Naydenov (dimitern) wrote :
Changed in juju-core:
status: Triaged → Won't Fix
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.