"destroy-environment" and /var/log/juju*

[John Meinel]

I'd just note that all the other providers don't act like this, so I don't
know that it is *predictable*. (you can always copy your all-machines.log
off before you destroy your environment, like you would do everywhere else.)

Certainly, I thought the point of "juju destroy-environment" was to get rid
of all the stuff related to the environment, and all-machines.log can be
>GB in size if you're poking a lot of stuff. I realize this is my bias, but
I would expect more surprise from people expecting things to be cleaned up
than people benefiting from having it left there. (Having it as a flag
could be interesting, destroy-environment --write-log-to $PATH.)

John
=:->



On Mon, Mar 24, 2014 at 11:27 AM, Tim Penhey <tim.penhey at canonical.com>wrote:

> On 24/03/14 18:48, John Meinel wrote:
> > I just did a "juju destroy-environment -y local" and it did kill the
> > agents, but it left the /var/log/juju-jameinel-local directory lying
> around.
> > It also left ~/.juju/local/ (with storage and db dirs), though the log
> > dir is gone.
>
> That was by design, as the all-machines log is useful to have around to
> diagnose issues even once the environment has been destroyed.
>
> There is code to clean it up when starting a new environment.
>
> Tim
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140324/59afc1dc/attachment.html>