[Python-modules-team] Bug#873179: awscli: All "aws ec2" commands fail with "get_environ_proxies() [...]"

Sebastien Delafond seb at debian.org
Fri Aug 25 10:50:11 UTC 2017

Package: awscli
Version: 1.11.139-1
Severity: important

With AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY properly exported, and
no '.*(proxy|PROXY).*' environment variables, all my aws ec2 commands
fail in the same exact fashion:

  # aws ec2 --region us-east-1 describe-instances --instance-ids [...]

  get_environ_proxies() missing 1 required positional argument: 'no_proxy'

I have another sid system where "aws ec2" is fully fonctional, and the
only difference I could readily identify was python3-requests (a
python3-botocore dependency) being 2.12.4-1 instead of
2.18.1-1. However, downgrading to that on the affected system does not
fix the issue.

I could not find any reference to the error message anywhere, so I'm
filing this bug so it can be first indexed, and hopefully later triaged



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages awscli depends on:
ii  python3             3.5.3-3
ii  python3-botocore    1.5.84-1
ii  python3-colorama    0.3.7-1
ii  python3-docutils    0.13.1+dfsg-2
ii  python3-rsa         3.4.2-1
ii  python3-s3transfer  0.1.10-1
ii  python3-yaml        3.12-1+b1
pn  python3:any         <none>

awscli recommends no packages.

awscli suggests no packages.

-- no debconf information

More information about the Python-modules-team mailing list