Re: Juju 2.0-rc3 is here!

'"upload-tools strikes back" > cannot upgrade with streams' > https://bugs.launchpad.net/juju/+bug/1631529 > > On Fri, Oct 7, 2016 at 1:51 PM, Matt Rae <matt@canonical.com> wrote: > > Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3. > > &

Re: Juju 2.0-rc3 is here!

Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3. Should 'juju upgrade-juju -m default' upgrade to rc3? So far I'm seeing 'no upgrades available' $ juju model-config agent-version 2.0-rc2 $ juju --version 2.0-rc3-xenial-amd64 $ juju upgrade-juju no upgrades available $ juju upgrade-juju

Re: Automatic hook retries in Juju 2.0

Hi Adam, I've also found that debugging environments was difficult with hook retrying on. I've disabled it like this: juju set-model-config automatically-retry-hooks=false On Thu, Jun 30, 2016 at 11:05 AM, Adam Collard wrote: > Did we get a way of disabling this

Re: getting rid of all-machines.log

Many operations teams already have a standard log collecting systems. I think it would be best to be flexible enough to work in environments with existing systems. Standard ways are logging to syslog so any syslog implementation can be used, or logging to stdout so a supervisor like djb