Bug 1578083
Summary: | aws s3 cp fails with: __init__() got an unexpected keyword argument 'max_bandwidth' | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Andy Grimm <agrimm> | |
Component: | python-s3transfer | Assignee: | Oyvind Albrigtsen <oalbrigt> | |
Status: | CLOSED ERRATA | QA Contact: | Brandon Perkins <bperkins> | |
Severity: | urgent | Docs Contact: | Vladimír Slávik <vslavik> | |
Priority: | urgent | |||
Version: | 7.5 | CC: | aherr, ajz, anrussel, cfeist, gfa, jnewbigin, jon.dufresne, karel.klic, leomar, mike, polpot78, rhbugs, rhbz, thomas.oulevey, vslavik | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | python-s3transfer-0.1.13-1.el7 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the "python-s3transfer" library introduced the "max_bandwidth" parameter in a new upstream version 0.1.12, and the updated "awscli" package expected this version to be available. As a consequence, using the "aws s3 cp" command with the non-updated "python-s3transfer" failed. The "aws" command has been modified to not use "max_bandwidth". As a result, the "aws s3 cp" command works again.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1581136 1581138 (view as bug list) | Environment: | ||
Last Closed: | 2018-10-30 10:12:40 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1581136, 1581138 |
Description
Andy Grimm
2018-05-14 18:50:40 UTC
Why has the progress on this one stopped? Echoing the previous comment, why is this stuck in QA? The fix for the 7.4.z version in RHBA-2018:1760 was released nearly a month ago on 2018-05-29 (and the 7.4 EUS awscli package was released 7 days after RHEL 7.5 in RHEA-2018:1163). This has an impact since EPEL deleted their version, so no downgrade is possible and causes issues with bootstrapping instances that need to retrieve data from S3. Because this bz is targeted for 7.6. The following bz is for backport to 7.5: https://bugzilla.redhat.com/show_bug.cgi?id=1581138 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3123 |