juju cannot deploy when distro-info-data gets a new series

[Curtis Hovey]

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/distro-info-data/ubuntu.csv, we saw it could not deploy local containers, maybe any machines:

machines:
  "0":
    agent-state: started
    agent-version: 1.23-alpha1.1
    dns-name: localhost
    instance-id: localhost
    series: vivid
    state-server-member-status: has-vote
  "1":
    agent-state-info: invalid series "angsty"
    instance-id: pending
    series: vivid
  "2":
    agent-state-info: invalid series "angsty"
    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.

[Curtis Hovey (sinzui)]

This is the distro line we added
17.04,Angsty Antelope,angsty,2016-10-23,2017-04-30,2018-01-29

[Curtis Hovey (sinzui)]

I removed the line from the vivid machine because we don't want to taint the lxc local test
I updated the vivid unit test to run in lxc. While lxc is not ideal, the suite isn't passing for other reasons so there is no substantial loss.

[Curtis Hovey (sinzui)]

Attached is the all-machines.log from a failed test

[Curtis Hovey (sinzui)]

See the duplicate bug 1434092 for details to fix this issue.

[Curtis Hovey (sinzui)]

Per Oleg Strikov "I'm helping rbasak with 1.22 packaging for vivid. One of autopkgtests for juju fails due to this bug and it's kinda blocker for packaging"

[Aaron Bentley (abentley)]

Landed for 1.22 in https://github.com/juju/juju/pull/1922