Bug 1927814
| Summary: | Rebase python-dogpile-cache to 1.1.2 | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Moises Guimaraes <moguimar> | |
| Component: | python-dogpile-cache | Assignee: | shreshtha joshi <shrjoshi> | |
| Status: | CLOSED ERRATA | QA Contact: | nlevinki <nlevinki> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 16.2 (Train) | CC: | amoralej, apevec, jagee | |
| Target Milestone: | beta | Keywords: | Triaged | |
| Target Release: | 16.2 (Train on RHEL 8.4) | |||
| Hardware: | All | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | python-dogpile-cache-1.1.2-1.el8ost | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1927815 (view as bug list) | Environment: | ||
| Last Closed: | 2021-09-15 07:11:47 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: | 1761768, 1989732 | |||
|
Description
Moises Guimaraes
2021-02-11 15:44:15 UTC
python-dogpile-cache-1.1.2 has been built in CBS for Centos 8 https://cbs.centos.org/koji/buildinfo?buildID=31946 and will be updated in RDO for Wallaby (it's still WIP). The version of dogpile.cache in uppper-constraints.txt for stable/train is 0.9.0 and the feature requiring this is not being backported upstream to train, so i'd prefer not to update python-dogpile-cache in RDO Train and make it downstream only. Reading the changelog for dogpile.cache: https://dogpilecache.sqlalchemy.org/en/latest/changelog.html The reason to do major bump from 0.9.0 to 1.0.0 was to remove support for python2 but reading all changes there seems not to have backwards incompatible changes that may break us. Also note that the update from version 0.9.2 to > 1 in oslo.cache didn't require any code change: https://review.opendev.org/c/openstack/oslo.cache/+/745509 So I'd say it looks like good candidate to update even if it's breaking upper-constraints.txt 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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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/RHEA-2021:3483 |