juju cannot deploy when distro-info-data gets a new series
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth | ||
1.22 |
Fix Released
|
Critical
|
Ian Booth | ||
1.23 |
Fix Released
|
High
|
Ian Booth |
Bug Description
Because the test suite breaks every six months when a new Ubuntu series is created. CI was updated to container a false series to catch defective tests when they are written. We have found a worse scenario though.
On a machine with angsty added to /usr/share/
machines:
"0":
agent-state: started
agent-version: 1.23-alpha1.1
dns-name: localhost
instance-id: localhost
series: vivid
state-
"1":
agent-
instance-id: pending
series: vivid
"2":
agent-
instance-id: pending
series: vivid
We are concerned that when Ubuntu W is added in a few months, every production juju env running j1.20, 1.21, or 1.22 state-servers will fail.
Related branches
Changed in juju-core: | |
milestone: | 1.21.4 → 1.24-alpha1 |
Changed in juju-core: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
This is the distro line we added angsty, 2016-10- 23,2017- 04-30,2018- 01-29
17.04,Angsty Antelope,