[SRU] awscli not kept up to date

This bug affects all suites to some extent, excluding groovy-proposed, and the package version is more outdated for the older supported releases, e.g. xenial and bionic.

The versions in the archive for xenial and bionic, 1.11 and 1.14, respectively, lack functionality applicable to newer AWS features, for example `aws eks wait` and `aws eks describe-cluster`.

CPC would like to see version 1.18.46 in groovy-proposed backported to all supported suites. SRU template incoming.

Sponsored for focal, eoan, bionic and xenial.

Note to SRU team: as mentioned in the bug description, this upload requires a new python-botocore. Those have been uploaded to the Unapproved queues as well and need to be accepted before considering these uploads here.

blocking this for eoan and earlier due to the 'incomplete' status of the matching python-botocore bug.

it's stated that a new python-botocore is required, but there is no corresponding change to the package dependencies in debian/control. The dependency on python3-botocore must be updated to have the correct version in SRU. Rejecting the current set of uploads, please upload with the dependency fix.

An upload of awscli to focal-proposed has been rejected from the upload queue for the following reason: "Requires versioned dependency on python3-botocore".

An upload of awscli to eoan-proposed has been rejected from the upload queue for the following reason: "Requires versioned dependency on python3-botocore".

An upload of awscli to bionic-proposed has been rejected from the upload queue for the following reason: "versioned dep on python3-botocore is incorrect per upsteram".

An upload of awscli to xenial-proposed has been rejected from the upload queue for the following reason: "versioned dep on python3-botocore is incorrect per upstream".

Hello Graham, or anyone else affected,

Accepted awscli into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/awscli/1.18.69-1ubuntu0.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Graham, or anyone else affected,

Accepted awscli into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/awscli/1.18.69-1ubuntu0.18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Graham, or anyone else affected,

Accepted awscli into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/awscli/1.18.69-1ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Thank you for this, really appreciate it.

Followed testing steps for bionic:

- Enabled bionic-proposed
- Installed awscli/bionic-proposed and python3-botocore/bionic-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig (ran successfully and updated the local kube config)

Followed testing steps for focal:

- Enabled focal-proposed
- Installed awscli/focal-proposed and python3-botocore/focal-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig (ran successfully and updated the local kube config)

Followed testing steps for xenial:
- Enabled focal-proposed
- Installed awscli/focal-proposed and python3-botocore/focal-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig
  - This failed to run successfully. Got error:

An HTTP Client raised and unhandled exception: __init__() got an unexpected keyword argument 'ssl_context'

Hello Graham, or anyone else affected,

Accepted awscli into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/awscli/1.18.69-1ubuntu0.19.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Followed testing steps in a fresh eoan VM:

- Enabled eoan-proposed
- Installed awscli/eoan-proposed and python3-botocore/eoan-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig (ran successfully and updated the local kube config)

The verification of the Stable Release Update for awscli has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package awscli - 1.18.69-1ubuntu0.19.10.1

---------------
awscli (1.18.69-1ubuntu0.19.10.1) eoan; urgency=medium

  * SRU latest upstream version to 19.10 (LP: #1867673).
  * debian/control: bump the python3-botocore version dep to the one required by
    upstream (per setup.cfg). Do the same for python3-s3transfer.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 17 Jun 2020 10:42:53 +0200

This bug was fixed in the package awscli - 1.18.69-1ubuntu0.20.04.1

---------------
awscli (1.18.69-1ubuntu0.20.04.1) focal; urgency=medium

  * SRU latest upstream version to 20.04 (LP: #1867673).
  * debian/control: bump the python3-botocore version dep to the one required by
    upstream (per setup.cfg). Do the same for python3-s3transfer.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 17 Jun 2020 10:42:53 +0200

This bug was fixed in the package awscli - 1.18.69-1ubuntu0.18.04.1

---------------
awscli (1.18.69-1ubuntu0.18.04.1) bionic; urgency=medium

  * SRU latest upstream version to 18.04 (LP: #1867673).
  * debian/control: bump the python3-botocore version dep to the one required by
    upstream (per setup.cfg). Do the same for python3-s3transfer.
  * debian/control: tweak the debhelper requirements.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 17 Jun 2020 10:42:53 +0200

Followed testing steps for xenial:
- Enabled focal-proposed
- Installed awscli/focal-proposed and python3-botocore/focal-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig (ran successfully and showed valid error messages, as I do not have an AWS account EKS cluster)

The "unhandled exception" reported by David in previous test runs on xenial is gone, using python-botocore from LP: #1875485. But I could not verify the local kube config is actually updated, as I do not have an AWS account nor EKS cluster. I'm not sure if this is enough or if we need somebody else to re-verify this:

root@namely-premium-longhorn:~# aws eks update-kubeconfig
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: the following arguments are required: --name

root@namely-premium-longhorn:~# aws eks --region us-east-1 update-kubeconfig --name test_cluster
Unable to locate credentials. You can configure credentials by running "aws configure".

root@namely-premium-longhorn:~# aws configure
AWS Access Key ID [None]: 123
AWS Secret Access Key [None]: 123
Default region name [None]: us-east-1
Default output format [None]:

root@namely-premium-longhorn:~# aws eks --region us-east-1 update-kubeconfig --name test_cluster

An error occurred (UnrecognizedClientException) when calling the DescribeCluster operation: The security token included in the request is invalid.

I ran the following quick test against a real EKS cluster,
and everything seemed to work as expected:

xenial $ # Enable proposed
xenial $ sudo apt-get install -y \
    awscli/xenial-proposed \
    python3-botocore/xenial-proposed \
    python3-s3transfer/xenial-proposed
[..snip..]
xenial $ aws iam get-user
# Returned expected user information
xenial $ sudo snap install kubectl --classic
[..snip..]
xenial $ aws eks update-kubeconfig --name eks-1-17-cluster
Added new context [..snip..]:cluster/eks-1-17-cluster to /home/ubuntu/.kube/config
xenial $ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 4m8s

This bug was fixed in the package awscli - 1.18.69-1ubuntu0.16.04.1

---------------
awscli (1.18.69-1ubuntu0.16.04.1) xenial; urgency=medium

  * SRU latest upstream version to 16.04 (LP: #1867673).
  * debian/control: bump the python3-botocore version dep to the one required by
    upstream (per setup.cfg). Do the same for python3-s3transfer.
  * debian/control: tweak the debhelper requirements.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 17 Jun 2020 10:42:53 +0200