Bug 1730912
Summary: | awscli not upgradable due to pyyaml being too new | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kevin Fenzi <kevin> |
Component: | awscli | Assignee: | David Duncan <davdunc> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | bperkins, davdunc, eparis, gary.buhrmaster, home, james.hogarth, jdiaz, jmatthew, jmmahler, jon.dufresne, kevin, me, mzink, pbrobinson, yogeshsharma, znmeb |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | awscli-1.16.263-2.fc31 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-26 17:27:11 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
Kevin Fenzi
2019-07-17 20:53:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. Requesting help on this from aws-sdk team. https://github.com/aws/aws-cli/pull/4403 - Bumped the version to 5.2. Any update on this as the Fedora 31 is unable to access AWS components from any scripts. Updated and completed. Upstream fix in place. Are there any plans to fix this in F31 or do we need to wait to f32 for the fixes. *** Bug 1758555 has been marked as a duplicate of this bug. *** This still uninstallable and I don't even see any test builds of the upstream release that fixes this https://apps.fedoraproject.org/packages/awscli/builds/ We're about to enter FinalFreeze with GA only a couple of weeks away. This is a key tool for a large number of people. What's the plan to fix this? Will a ProvenPackager need to intervene to ensure that it isn't broken when F31 releases? I've carried out a scratch build of the current rawhide spec for this and python-botocore against the F31-candidate target: * https://koji.fedoraproject.org/koji/taskinfo?taskID=38119003 * https://koji.fedoraproject.org/koji/taskinfo?taskID=38118574 I've verified that these are installable in F31 (note that I had to bump the botocore_version requirement as rawhide has the botocore version out of sync with the expected version in the awscli spec/setuptools ... do these have to be so tightly bound together? If so can I please suggest a %check or a BuildRequires to enforce that this check is in place to prevent an awscli being built without a matching botocore available?): ``` [james.hogarth@localhost awscli]$ sudo dnf install https://kojipkgs.fedoraproject.org//work/tasks/9057/38119057/awscli-1.16.252-1.fc31.noarch.rpm https://kojipkgs.fedoraproject.org//work/tasks/8623/38118623/python3-botocore-1.12.243-1.fc31.noarch.rpm Last metadata expiration check: 0:13:14 ago on Mon 07 Oct 2019 15:19:27 BST. awscli-1.16.252-1.fc31.noarch.rpm 318 kB/s | 1.4 MB 00:04 python3-botocore-1.12.243-1.fc31.noarch.rpm 389 kB/s | 3.3 MB 00:08 Dependencies resolved. ============================================================================================================================================================================================================================================== Package Architecture Version Repository Size ============================================================================================================================================================================================================================================== Installing: awscli noarch 1.16.252-1.fc31 @commandline 1.4 M Upgrading: python3-botocore noarch 1.12.243-1.fc31 @commandline 3.3 M Transaction Summary ============================================================================================================================================================================================================================================== Install 1 Package Upgrade 1 Package Total size: 4.7 M Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Upgrading : python3-botocore-1.12.243-1.fc31.noarch 1/3 Installing : awscli-1.16.252-1.fc31.noarch 2/3 Cleanup : python3-botocore-1.12.188-2.fc31.noarch 3/3 Running scriptlet: python3-botocore-1.12.188-2.fc31.noarch 3/3 Verifying : awscli-1.16.252-1.fc31.noarch 1/3 Verifying : python3-botocore-1.12.243-1.fc31.noarch 2/3 Verifying : python3-botocore-1.12.188-2.fc31.noarch 3/3 Upgraded: python3-botocore-1.12.243-1.fc31.noarch Installed: awscli-1.16.252-1.fc31.noarch Complete! ``` Incidentally the changelog for these are in the wrong format and need fixing whilst the F31 update is being carried out anyway ... The missing brackets on the email are causing the parsing to break: * https://apps.fedoraproject.org/packages/awscli/changelog/ * https://apps.fedoraproject.org/packages/python3-botocore/changelog/ tested, works for me. There was an issue with the cli build in the current version. 1.16.253 is being built now. I can't get the awscli-1.16.253-2.fc32 package to install on f31 because of all sorts of python dependency issues. Any chance you could rebuild awscli-1.16.198-2.fc31 with the spec fix so we had something in 31? Thank you! David you need to build a fixed version for F31, not just build for Rawhide. We're now in FinalFreeze with an uninstallable awscli on F31 Are you going to be able to resolve this? The schedule has the actual release in a week, this needs to be fixed ASAP if awscli is going to be installable at release, and if upgrades are not going to break (or remove awscli). @Eric: I'm not sure what "CLI" issue David is referring to, but you can give my scratch build in koji linked previously a go at need. Oh and the changelog is still the wrong format ... please fix it so the tools can properly parse it. (In reply to David Duncan from comment #12) > There was an issue with the cli build in the current version. 1.16.253 is > being built now. Any reason not to "git merge master" this for F-31, as it's not install-able there ATM? Still not working in F31 beta - I'm dropping back to a container to run `aws-cli` Okay this has gone on long enough I think ... I'll fix this up myself as an urgent issue. David feel free to contact me directly if you'd like to discuss ways to avoid this happening in future. FEDORA-2019-94473553fc has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-94473553fc Since this is so close to release the auto-stable time is 7 days in bodhi but the karma threshold is only 3. Please test the update and provide feedback to get the fix out ASAP. awscli-1.16.263-2.fc31, python-botocore-1.12.253-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-94473553fc Hi james, thanks for fixing this. I apologize for missing on it. I was confused about the build process. I am typically building a new one for rawhide ~daily now, but I am not backporting any changes since this is such a fast moving project. This relax-dependencies patch requirement has been removed as a result of an upstream decision to remove the ceilings from the versions. I couldn't get it to work from testing - probably the mirror hasn't updated yet. But I did get it installed and working from https://bodhi.fedoraproject.org/updates/FEDORA-2019-94473553fc awscli-1.16.263-2.fc31, python-botocore-1.12.253-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |