** Changed in: juju-core (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1284127
Title:
juju 1.17.2 client doesn't like juju 1.17.3
** Changed in: juju-core (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284127
Title:
juju 1.17.2 client doesn't like juju 1.17.3 .jenv files
To manage
** Summary changed:
- juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client
+ juju 1.17.2 client doesn't like juju 1.17.3 .jenv files
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
The specific bug doesn't have to do with streams or any such thing. As
Andrew mentioned, it is just that we changed the default values for an
item in the environment configuration, and 1.17.2 didn't like the
content being the empty string.
The way to fix that is to not use 1.17.2. So I think
Marked Won't Fix because it is technically a bug in 1.17.2's
interpretation of a newer config, 1.16 didn't have that field so it
isn't a stable release compatibility problem.
** Changed in: juju-core
Status: Triaged = Won't Fix
--
You received this bug notification because you are a
** Summary changed:
- juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client
+ juju 1.17.2 client doesn't like juju 1.17.3 .jenv files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The specific bug doesn't have to do with streams or any such thing. As
Andrew mentioned, it is just that we changed the default values for an
item in the environment configuration, and 1.17.2 didn't like the
content being the empty string.
The way to fix that is to not use 1.17.2. So I think
Marked Won't Fix because it is technically a bug in 1.17.2's
interpretation of a newer config, 1.16 didn't have that field so it
isn't a stable release compatibility problem.
** Changed in: juju-core
Status: Triaged = Won't Fix
--
You received this bug notification because you are a