Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
AWS users who had the Fedora EPEL copy of awscli installed prior to the update to RHEL 7.5 are left with a non-functional aws command when yum update'd to 7.5.
Version-Release number of selected component (if applicable):
awscli-1.14.28-5.el7
How reproducible:
Always
Steps to Reproduce:
1. Install EPEL copy of awscli-1.11.133-1.el7 package to reproduce what an existing user will already have. This pulls in python-colorama python-docutils python-pillow python2-botocore python2-futures python2-jmespath python2-rsa python2-s3transfer
2. `yum update awscli` to pull in base copy of awscli at 1.14.28-5.el7
3. Run `aws`
Actual results:
aws produces stacktrace and dies:
# aws
Traceback (most recent call last):
File "/bin/aws", line 19, in <module>
import awscli.clidriver
File "/usr/lib/python2.7/site-packages/awscli/clidriver.py", line 25, in <module>
from botocore.history import get_global_history_recorder
ImportError: No module named history
After `yum swap python2-s3transfer python-s3transfer` the aws command functions as expected.
Expected results:
aws command works
Additional info:
The problem is due to incompatible python2-s3transfer vs python-s3transfer packages. All existing awscli users will be left with a non-functional command after the yum update to the RHEL base copy. Running `yum swap python2-s3transfer python-s3transfer` will fix this but ideally it would be better not to break things in the first place. I suspect the best solution to this would be for awscli to Require: python-s3transfer directly or for python-s3transfer to Obsolete: python2-s3transfer.
For those EPEL users that are already affected, the way to fix this is
yum update awscli
yum swap python2-s3transfer python-s3transfer
At this point you may well have unnecessary packages installed as the depchain is different between the two versions and you can probably uninstall python-colorama python2-rsa python2-boto3 python2-botocore python2-futures python2-jmespath python2-rsa python2-s3transfer which were all installed by the EPEL awscli.
This is sadly another example of when a package is moved from EPEL to the main OS and the upgrade isn't transparent, see https://bugzilla.redhat.com/show_bug.cgi?id=1492884 for another example.
I thought the whole point of using RHEL was stability, I'd expect this sort of thing in Fedora.
Comment 9RHEL Program Management
2021-02-15 07:38:51 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: AWS users who had the Fedora EPEL copy of awscli installed prior to the update to RHEL 7.5 are left with a non-functional aws command when yum update'd to 7.5. Version-Release number of selected component (if applicable): awscli-1.14.28-5.el7 How reproducible: Always Steps to Reproduce: 1. Install EPEL copy of awscli-1.11.133-1.el7 package to reproduce what an existing user will already have. This pulls in python-colorama python-docutils python-pillow python2-botocore python2-futures python2-jmespath python2-rsa python2-s3transfer 2. `yum update awscli` to pull in base copy of awscli at 1.14.28-5.el7 3. Run `aws` Actual results: aws produces stacktrace and dies: # aws Traceback (most recent call last): File "/bin/aws", line 19, in <module> import awscli.clidriver File "/usr/lib/python2.7/site-packages/awscli/clidriver.py", line 25, in <module> from botocore.history import get_global_history_recorder ImportError: No module named history After `yum swap python2-s3transfer python-s3transfer` the aws command functions as expected. Expected results: aws command works Additional info: The problem is due to incompatible python2-s3transfer vs python-s3transfer packages. All existing awscli users will be left with a non-functional command after the yum update to the RHEL base copy. Running `yum swap python2-s3transfer python-s3transfer` will fix this but ideally it would be better not to break things in the first place. I suspect the best solution to this would be for awscli to Require: python-s3transfer directly or for python-s3transfer to Obsolete: python2-s3transfer.