localHTTPSServerSuite.TestMustDisableSSLVerify fails in lxc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Curtis Hovey |
Bug Description
We want to run the unit test suit in lxc because we think we can bring them up quicker on dedicated machines and easilly cleanup after a disaster. The localHTTPSServe
FAIL: local_test.go:958: localHTTPSServe
Started service at: https:/
Set tools-metadata-
Set image-metadata-
[LOG] 0:00.150 INFO juju.provider.
[LOG] 0:00.234 INFO juju.provider.
local_test.go:970:
c.Assert(err, gc.ErrorMatches, "(.|\n)*x509: certificate signed by unknown authority")
... error string = "" +
... "cannot make Swift control container: failed to create container: juju-test-
... "caused by: authentication failed\n" +
... "caused by: failed executing the request https:/
... "caused by: Post https:/
... regex string = "" +
... "(.|\n" +
... ")*x509: certificate signed by unknown authority"
[LOG] 0:00.295 INFO juju.provider.
[LOG] 0:00.298 DEBUG juju.provider.
OOPS: 78 passed, 3 skipped, 1 FAILED
--- FAIL: Test (77.00 seconds)
FAIL
FAIL github.
Changed in juju-core: | |
milestone: | next-stable → 1.21-alpha1 |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
I may have some insight into this error, possibly a fix in the setup of unit-tests. I had a related bzr error in lxc. The installation of ca-certificates before running make check allowed the test to pass. Then I realised I was testing with a simple trusty lxc instead of the juju-trusty- template container. The latter fails in different ways than the former. But but but we may be close to identifying additional install-build-deps that we tend to have on desktop and server images, but not in cloud images.