Open Stack

Le lun. 5 sept. 2022 à 16:37, Előd Illés <elod.illes at est.tech> a écrit :

> Hi,
>
> With the latest oslo.db 12.1.0 release it seems multiple repositories are
> broken (see the corresponding requirements patch [1] for details, and
> probably there are more, that are not tested within requirements
> repository). The patch that introduces the break [2] "is necessary for
> oslo.db and openstack applications in general to be able to run on
> SQLAlchemy 2.0" according to patch author.
>
> Since we are after the 3rd milestone of Zed, we have very limited time to
> figure out what to do. The 2 options are:
>
> 1) fix every broken repository to work with oslo.db 12.1.0
>     as far as we know this is quite impossible as for some repositories
> the already existing fixes took almost a cycle to be implemented and there
> are still undiscovered bugs around this. (we don't know if this is really
> true, or probably there are cases where it's easy to fix)
>
> 2) revert the breaking change [2] and do another release in oslo.db now
> without it (and add it back after Zed release & release oslo.db with it as
> soon as possible in Antelope cycle)
>     as far as we understand this does not cause any issue for those who
> already adapted to oslo.db 12.1.0, so this should not be painful
>


>From a personal point of view, I'm on board with option 2, which closes the
race as soon as we revert and gives us more time to find the root cause and
fix it correctly.
>From a Nova/Placement PoV, they're not impacted, as we only raise warnings,
so feel free to pick any other project to discuss about option 1.

-Sylvain

> Based on the above Release team is opting toward the 2nd option.
>
> Please let us know your opinion!
>
> [1] https://review.opendev.org/c/openstack/requirements/+/855153/
> [2] https://review.opendev.org/c/openstack/oslo.db/+/804775
>
> Thanks,
>
> Előd
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220905/f6b58fd2/attachment.htm>