Bug 2101550

Summary: awscli broken after updating
Product: Red Hat Enterprise Linux 7 Reporter: redhat
Component: awscliAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED DUPLICATE QA Contact: cluster-qe <cluster-qe>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.9Flags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-28 07:14:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description redhat 2022-06-27 19:13:54 UTC
Description of problem:
It appears that the latest python-s3transfer updated from 0.1.13-1.el7.0.1 to 0.1.13-1.el7_9.2 and removed botocore docevents from the bundle which broke awscli I'm not sure what else may be missing but you can see the error by simply running aws --version 
 
Version-Release number of selected component (if applicable):


How reproducible:
aws --version

Steps to Reproduce:
1. install awscli
2.
3.

Actual results:

 aws --version
Traceback (most recent call last):
  File "/usr/bin/aws", line 19, in <module>
    import awscli.clidriver
  File "/usr/lib/python2.7/site-packages/awscli/clidriver.py", line 37, in <module>
    from awscli.help import ProviderHelpCommand
  File "/usr/lib/python2.7/site-packages/awscli/help.py", line 24, in <module>
    from botocore.docs.bcdoc import docevents
ImportError: cannot import name docevents

Expected results:
Something like this:
aws --version
aws-cli/1.14.28 Python/2.7.5 Linux/3.10.0-1160.66.1.el7.x86_64 botocore/1.8.35

Additional info:

Comment 3 redhat 2022-06-27 20:05:12 UTC
Can you give us access to RHELPLAN-126388? It appears that we don't have permission to it.

Comment 4 Oyvind Albrigtsen 2022-06-28 07:14:12 UTC
The RHELPLAN is just for internal tracking I think.

The issue is being fixed in https://bugzilla.redhat.com/show_bug.cgi?id=2073979.

*** This bug has been marked as a duplicate of bug 2073979 ***