Deployer 0.7.1 on trusty cannot talk to Juju2 because :tlsv1 alert protocol version
Bug #1576695 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Critical
|
Unassigned | ||
juju-deployer |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
As seen in
http://
Deployer cannot talk to Juju2 (on maas2) because :tlsv1 alert protocol version
This issue relates to bug 1443704 in Ubuntu trusty. trusty's py 3.4 does support PROTOCOL_TLSv1_2.
Related branches
lp:~tvansteenburgh/juju-deployer/python3-support
- juju-deployers: Pending requested
-
Diff: 3879 lines (+261/-2524)43 files modified.bzrignore (+1/-0)
HACKING (+3/-2)
Makefile (+1/-9)
deployer/action/diff.py (+8/-5)
deployer/action/export.py (+1/-0)
deployer/action/importer.py (+4/-1)
deployer/charm.py (+4/-2)
deployer/cli.py (+5/-3)
deployer/config.py (+10/-8)
deployer/deployment.py (+20/-17)
deployer/env/__init__.py (+0/-3)
deployer/env/base.py (+2/-1)
deployer/env/go.py (+5/-4)
deployer/env/mem.py (+5/-3)
deployer/env/py.py (+1/-3)
deployer/env/watchers.py (+2/-1)
deployer/errors.py (+4/-2)
deployer/feedback.py (+5/-0)
deployer/guiserver.py (+1/-0)
deployer/relation.py (+3/-4)
deployer/service.py (+14/-10)
deployer/tests/base.py (+5/-2)
deployer/tests/mock.py (+0/-2367)
deployer/tests/test_base.py (+4/-2)
deployer/tests/test_charm.py (+2/-1)
deployer/tests/test_config.py (+20/-12)
deployer/tests/test_constraints.py (+8/-5)
deployer/tests/test_deployment.py (+19/-11)
deployer/tests/test_diff.py (+8/-5)
deployer/tests/test_goenv.py (+2/-1)
deployer/tests/test_guienv.py (+1/-0)
deployer/tests/test_guiserver.py (+1/-0)
deployer/tests/test_importer.py (+10/-7)
deployer/tests/test_pyenv.py (+4/-2)
deployer/tests/test_service.py (+1/-0)
deployer/tests/test_utils.py (+13/-10)
deployer/tests/test_watchers.py (+16/-7)
deployer/utils.py (+11/-5)
deployer/vcs.py (+6/-8)
doc/conf.py (+1/-0)
setup.py (+6/-1)
test-requirements.txt (+4/-0)
tox.ini (+20/-0)
lp:~tvansteenburgh/python-jujuclient/tlsv1_2
- juju-deployers: Pending requested
-
Diff: 66 lines (+19/-5)2 files modifiedjujuclient.py (+10/-1)
test_jujuclient.py (+9/-4)
summary: |
- Deployer cannot talk to Juju2 (on maas2) because :tlsv1 alert protocol + Deployer 2 cannot talk to Juju2 (maa 1.9) because :tlsv1 alert protocol version |
summary: |
- Deployer 2 cannot talk to Juju2 (maa 1.9) because :tlsv1 alert protocol + Deployer 2 on trusty cannot talk to Juju2 because :tlsv1 alert protocol version |
description: | updated |
description: | updated |
tags: | added: python2.7 |
Changed in juju-core: | |
status: | Triaged → Invalid |
summary: |
- Deployer 2 on trusty cannot talk to Juju2 because :tlsv1 alert protocol - version + Deployer 0.7.1 on trusty cannot talk to Juju2 because :tlsv1 alert + protocol version |
Changed in juju-deployer: | |
status: | New → In Progress |
Changed in juju-deployer: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | 2.0-beta7 → none |
Changed in juju-deployer: | |
milestone: | none → 0.8.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is almost certainly because this is running on trusty, which uses python 2.7.6, and thus doesn't have TLS 1.2, as noted here: https:/ /bugs.launchpad .net/ubuntu/ +source/ python2. 7/+bug/ 1443704