If I understand this correctly, this seems to be an issue related to a backward incompatible change in the Python websocket client library. Its API changed in version 1.13, trusty has 1.12, vivid updated to 1.18 [1]. Basically they introduced SSL certs validation by default [2]. Quickstart reacted to this change in [3], assuming 1.18 was going to be included in utopic. Note that the Juju stable PPA includes version 1.18 for all supported series [4]. The quickstart update was released as version 1.4.3, and that would explain why you are encountering that failure with 1.4.2 on vivid. That said, I think we need to include a newer Quickstart version in vivid. I am not sure about 1.4.2 working on older Juju versions: if the above is correct this is a client issue not affecting juju-core itself.
[1] http://packages.ubuntu.com/search?keywords=python-websocket&searchon=names&suite=all§ion=all [2] https://github.com/liris/websocket-client/pull/56 [3] http://bazaar.launchpad.net/~juju-gui/juju-quickstart/trunk/revision/98 [4] https://launchpad.net/~juju/+archive/ubuntu/stable/+packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-quickstart in Ubuntu. https://bugs.launchpad.net/bugs/1408280 Title: juju-quickstart fails with SSL verification errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1408280/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
