Comment 1 for bug 1705112

It sounds like you upgraded the controller but not the models. Are you
having units in the controller model? Or is this a case of needing to also
run "juju upgrade-juju -m default" (or any other model name you have
created)

John
=:->

On Jul 18, 2017 22:21, "Jorge Niedbalski" <email address hidden>
wrote:

> ** Summary changed:
>
> - Agent.conf upgradedToVersion field not updated on upgrades
> + Agent.conf upgradedToVersion field not updated on upgrade
>
> ** Description changed:
>
> [Environment]
>
> - Xenial
> + Xenial
> Juju 2.2.2
>
> [Description]
>
> -
> - $ juju upgrade-juju -m controller --agent-version='2.2.2'
> + $ juju upgrade-juju -m controller --agent-version='2.2.2'
>
> - Check /var/lib/juju/agents/machine-XX/agent.conf value has been set to
> upgradedToVersion: 2.2.2.
>
> - - Same check for /var/lib/juju/agents/unit-*/agent.conf keeps in
> + - Same check for /var/lib/juju/agents/unit-*/agent.conf keeps
> referring the previous release upgradedToVersion: 2.1.3
>
> The upgrade seems successful except from this field on the agent.conf.
>
> ** Tags added: sts
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1705112
>
> Title:
> Agent.conf upgradedToVersion field not updated on upgrade
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1705112/+subscriptions
>