On Wed, 2022-09-28 at 12:34 +0200, Balazs Gibizer wrote: > Hi, > > So we have a bug[1] that was fixed in oslo.concurrency on master[2] and > released as 5.0.1 and Zed is released with 5.0.1. > > The issue is present in stable/yoga as well. There we have > oslo.concurrency upper constraint pinned to 4.5.0 [3]. > > 1) How can I backport [2] to the 4.5.x series of oslo.concurrency to > release 4.5.2 with the fix? I don't see a branch that I could use for > this. I don't have answers for you but I can say that the reason for this is because oslo.concurrency has been using the independent release model for some time now [1]. We won't have stable branches (or any kind of long-lived release branch) without manually creating them. Stephen [1] https://review.opendev.org/c/openstack/releases/+/764624 > > 2) If #1) is solved and 4.5.2 is released can I propose an upper > constraint bump on stable/yoga from 4.5.0 to 4.5.2? > > 3) If #1) and #2) is done. Can I propose a minimum requirement bump in > nova's requirements.txt from >= 4.5.0 to >= 4.5.2 on stable/yoga? > > Cheers, > gibi > > [1] https://bugs.launchpad.net/nova/+bug/1988311 > [2] https://review.opendev.org/c/openstack/oslo.concurrency/+/855714 > [3] > https://github.com/openstack/requirements/blob/e64217c9f9316675f57e14ff559bb4de90bc6637/upper-constraints.txt#L26 > > >