configSuite.TestNewModelConfig test failure lxd

[John George]

Unit-test failure for configSuite.TestNewModelConfig as seen here:
http://reports.vapour.ws/releases/issue/56bd7c8e749a5636a1d818c9

config_test.go:221:
    if !c.Check(err, jc.ErrorIsNil) {
        ...
    }
... value *errors.Err = &errors.Err{message:"", cause:(*json.UnmarshalTypeError)(0xc82045e870), previous:(*errors.Err)(0xc820458a50), file:"github.com/juju/juju/provider/lxd/provider.go", line:29} ("can't connect to the local LXD server: json: cannot unmarshal number into Go value of type string")

[Curtis Hovey (sinzui)]

I expect this to be fixed when every host that tests lxd unit tests has the new lxd.

[Curtis Hovey (sinzui)]

This issue has returned because of bug 1559169. For the time being, the wily unit tests are non-voting :(

[Ian Booth (wallyworld)]

This is an external issue which appears fixed now that lxcfs has had a fix released

[Curtis Hovey (sinzui)]

This issue was actually fixed by a change to the wily unit test job to create an instance that installed the needed version of lxd. The Makefile does not install the correct version of lxd and the test suite wrongly assumes all version of lxd are valid to test with.