Comment 10 for bug 1765722

Note that if you've upgraded to 2.3.6 and are experiencing this bug it is
hard to get to a fixed version. Because the upgrade step itself is broken
it won't go past it to let it notice a new version to install.

It should be possible with some manual surgery to get rolled back to 2.3.5
or to get up to a 2.3.7 but the standard "juju upgrade-juju" won't work.

John
=:->

On Sun, Apr 22, 2018, 18:30 John A Meinel <email address hidden> wrote:

> https://github.com/juju/juju/pull/8638
>
> ** Also affects: juju/2.3
> Importance: Undecided
> Status: New
>
> ** Changed in: juju/2.3
> Importance: Undecided => Critical
>
> ** Changed in: juju/2.3
> Status: New => In Progress
>
> ** Changed in: juju/2.3
> Milestone: None => 2.3.7
>
> ** Changed in: juju/2.3
> Assignee: (unassigned) => John A Meinel (jameinel)
>
> ** Changed in: juju
> Milestone: 2.3.7 => 2.4-beta2
>
> --
> You received this bug notification because you are a bug assignee.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1765722
>
> Title:
> upgrade to 2.3.6 failed: the dotted field is not valid for storage
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1765722/+subscriptions
>