** Description changed: + [Original Bug Description] + awscli is not kept up to date, and so new AWS features are not available. The AWS pip installation method is unaudited and unsigned, and is not a production ready solution to the out-of-date problem. The awscli package needs to be kept up to date and available on all supported Ubuntu OSes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: awscli (not installed) ProcVersionSignature: Ubuntu 4.4.0-1100.111-aws 4.4.203 Uname: Linux 4.4.0-1100-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Mar 16 19:36:32 2020 Ec2AMI: ami-a8d2d7ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: awscli UpgradeStatus: No upgrade log present (probably fresh install) + + + [[ SRU Request Template ]] + + [Impact] + + * the awscli package is out of date to varying degrees across supported + Ubuntu releases + + + * old versions of awscli lack critical functionality for modern AWS + cloud features. For example, several `aws eks` commands are unavailable + and/or unsupported prior to version 1.18.17 [1]. + + * An updated awscli package will allow Xenial and Bionic, in + particular, to access modern AWS functionality from the archive. + + [Test Case] + + * on any ubuntu-release without groovy-proposed enabled, apt-get install awscli and attempt `aws eks update-kubeconfig`. + * This is functionality described in the AWS EKS getting started guide [1] as requiring version 1.18.17 or later [1], and is part of the documented web-console path to using Ubuntu (or any distro) on EKS. + * On the version of awscli in bionic (1.14.44), the `eks` subcommand is not available. + * On eoan or focal, this command may not correctly update the user's kubeconfig file depending on the configuration of their AWS EKS cluster (k8s version, cluster options, etc). + + * The latest version of this package is part of acceptance criteria of + AWS cloud images for Ubuntu CPC and cloud partners. + + [Regression Potential] + + * users of ubuntu and awscli who have scripting or automation reliant + on outdated versions of awscli are likely to see some form of breakage + insofar as AWS has been willing to break functionality of older + versions. + + * The latest version of awscli (1.18.47) lists botocore 1.15.47 as a + dependency; at the time of this description the version of python- + botocore in the archive does not meet this requirement [2] -- package + builds or installation could fail if this dependency is not correctly + resolved. + + * Any Ubuntu image builds which preinstall this package and/or use it + in boot scripts may break depending on their expectations. + + [Other Info] + + * The Hardware Enablement exception likely applies here, as updating this package version will enable using functionality of the AWS cloud which are impossible to use with the versions of the cli currently in the archive. + + [1] https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html + [2] https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485
** Summary changed: - awscli not kept up to date + [SRU] awscli not kept up to date ** Description changed: [Original Bug Description] awscli is not kept up to date, and so new AWS features are not available. The AWS pip installation method is unaudited and unsigned, and is not a production ready solution to the out-of-date problem. The awscli package needs to be kept up to date and available on all supported Ubuntu OSes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: awscli (not installed) ProcVersionSignature: Ubuntu 4.4.0-1100.111-aws 4.4.203 Uname: Linux 4.4.0-1100-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Mar 16 19:36:32 2020 Ec2AMI: ami-a8d2d7ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: awscli UpgradeStatus: No upgrade log present (probably fresh install) - [[ SRU Request Template ]] [Impact] - * the awscli package is out of date to varying degrees across supported + * the awscli package is out of date to varying degrees across supported Ubuntu releases - - * old versions of awscli lack critical functionality for modern AWS + * old versions of awscli lack critical functionality for modern AWS cloud features. For example, several `aws eks` commands are unavailable and/or unsupported prior to version 1.18.17 [1]. - * An updated awscli package will allow Xenial and Bionic, in + * An updated awscli package will allow Xenial and Bionic, in particular, to access modern AWS functionality from the archive. [Test Case] - * on any ubuntu-release without groovy-proposed enabled, apt-get install awscli and attempt `aws eks update-kubeconfig`. - * This is functionality described in the AWS EKS getting started guide [1] as requiring version 1.18.17 or later [1], and is part of the documented web-console path to using Ubuntu (or any distro) on EKS. - * On the version of awscli in bionic (1.14.44), the `eks` subcommand is not available. - * On eoan or focal, this command may not correctly update the user's kubeconfig file depending on the configuration of their AWS EKS cluster (k8s version, cluster options, etc). + * on any ubuntu release without groovy-proposed enabled: `apt-get install awscli` and attempt `aws eks update-kubeconfig`. + * This is functionality described in the AWS EKS getting started guide [1] as requiring version 1.18.17 or later [1], and is part of the documented web-console path to using Ubuntu (or any distro) on EKS. + * On the version of awscli in bionic (1.14.44), the `eks` subcommand is not available. + * On eoan or focal, this command may not correctly update the user's kubeconfig file depending on the configuration of their AWS EKS cluster (k8s version, cluster options, etc). - * The latest version of this package is part of acceptance criteria of + * The latest version of this package is part of acceptance criteria of AWS cloud images for Ubuntu CPC and cloud partners. [Regression Potential] - * users of ubuntu and awscli who have scripting or automation reliant + * users of ubuntu and awscli who have scripting or automation reliant on outdated versions of awscli are likely to see some form of breakage insofar as AWS has been willing to break functionality of older versions. - * The latest version of awscli (1.18.47) lists botocore 1.15.47 as a + * The latest version of awscli (1.18.47) lists botocore 1.15.47 as a dependency; at the time of this description the version of python- botocore in the archive does not meet this requirement [2] -- package builds or installation could fail if this dependency is not correctly resolved. - * Any Ubuntu image builds which preinstall this package and/or use it + * Any Ubuntu image builds which preinstall this package and/or use it in boot scripts may break depending on their expectations. [Other Info] - - * The Hardware Enablement exception likely applies here, as updating this package version will enable using functionality of the AWS cloud which are impossible to use with the versions of the cli currently in the archive. + + * The Hardware Enablement exception likely applies here, as updating + this package version will enable using functionality of the AWS cloud + which are impossible to use with the versions of the cli currently in + the archive. [1] https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html [2] https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867673 Title: [SRU] awscli not kept up to date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
