awscli now depends on python3-botocore >= 1.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
awscli (Debian) |
Fix Released
|
Unknown
|
|||
awscli (Ubuntu) |
Fix Released
|
Critical
|
Kamal Mostafa | ||
Xenial |
Fix Released
|
Critical
|
Kamal Mostafa | ||
Yakkety |
Fix Released
|
Critical
|
Kamal Mostafa | ||
Zesty |
Fix Released
|
Critical
|
Kamal Mostafa |
Bug Description
1) Description: Ubuntu 16.04.1 LTS
Release: 16.04
2) 1.11.13-1~16.04.0
3) Run aws (even just for cli help), no crash
4) Crashes
More info:
After the latest update of awscli to 1.11.13-1~16.04.0 on Xenial, aws crashes immediately with the following Python trace:
$ aws
Traceback (most recent call last):
File "/usr/bin/aws", line 27, in <module>
sys.
File "/usr/bin/aws", line 23, in main
return awscli.
File "/usr/lib/
return driver.main()
File "/usr/lib/
parser = self._create_
File "/usr/lib/
command_table = self._get_
File "/usr/lib/
self.
File "/usr/lib/
command_
File "/usr/lib/
return self._events.
File "/usr/lib/
return self._emit(
File "/usr/lib/
response = handler(**kwargs)
File "/usr/lib/
service_
File "/usr/lib/
return self._get_
File "/usr/lib/
api_version = self.session.
AttributeError: 'NoneType' object has no attribute 'get'
Upgrading to python3-botocore from xenial-updates (currently 1.4.70-1~16.04.0) solves the problem. This took out a number of our production instances which used the cli for SSH authentication.
-------
SRU Xenial/Yakkety justification
[Impact]
* awscli (1.11.13-1) and its dependencies including python3-botocore were
recently no-change-
python3-botocore versioned dependency is insufficient (needs a newer version
of python3-botocore than specified).
* If awscli is updated on Y or X (to version 1.11.13-1~whatever) without also
updating python3-botocore, the 'aws' command fails completely.
* The insufficient versioned dep is a bug in Debian and Zesty too (but don't
manifest since those only supply the newer python3-botocore version).
* To fix this, we've bumped up the versioned dep in Zesty's awscli
(1.11.
* The issue has also been bug reported in Debian.
[Test Case]
* On Y or X, manually update awscli to version (1.11.13-
do not update python3-botocore (leave it at version 1.3.23-1).
Run 'aws' and observe crash instead of expected command line usage/help
message.
[Regression Potential]
* None. This update _only_ increases the versioned dependency, so as to
force python3-botocore to update along with awscli.
Changed in awscli (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Critical |
tags: | added: xenial |
Changed in awscli (Ubuntu Zesty): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in awscli (Ubuntu Yakkety): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in awscli (Ubuntu Xenial): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in awscli (Ubuntu Zesty): | |
status: | Triaged → In Progress |
Changed in awscli (Ubuntu Yakkety): | |
status: | New → In Progress |
Changed in awscli (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in awscli (Debian): | |
status: | Unknown → New |
description: | updated |
Changed in awscli (Debian): | |
status: | New → Fix Released |
Can't be seen on a system that ran global updates, but makes sens if only awscli is updated/installed and still on the release.
I flagged critical for the risk of loosing logins.
Release came out with /launchpad. net/ubuntu/ yakkety/ amd64/python3- botocore/ 1.3.23- 1
https:/
I was not part of that work, but as far as I understand it that seems to be a regression of the SRU that was made. /launchpad. net/ubuntu/ +source/ awscli/ +publishinghist ory /launchpad. net/ubuntu/ +source/ python- botocore/ +publishinghist ory
https:/
https:/