Unit number is increasing in latest juju version.

[Simon Davy]

On 13 November 2015 at 13:50, Mark Shuttleworth <mark at ubuntu.com> wrote:
>
> Thanks Sunitha. Matty, deeper question is - was this an intended change
> in behaviour, and what's the rationale?

One possibility is that the juju environment is no longer being torn
down between tests? That would result in this behaviour, for sure.

So this could have been induced by an amulet change, or a local
change, perhaps, rather than a juju core change?

If the environment is being recreated each time, then perhaps juju
destrroy environment is somehow not cleaning up some state, and this
getting picked up in the new bootstrap somehow? Don't see any other
way that a fresh juju env would not start at /0.

Either way, Matty's fix is a more robust way to write amulet tests,
regardless. You don't really want to destroy/bootstrap your env
between every test, very slow.

HTH

Thanks

-- 
Simon