[openstack-dev] [mistral][oslo.messaging] stable/mitaka is broken by oslo.messaging 5.0.0

Doug Hellmann doug at doughellmann.com
Tue May 17 14:50:00 UTC 2016

Excerpts from Renat Akhmerov's message of 2016-05-17 19:10:55 +0700:
> Team,
> Our stable/mitaka branch is now broken by oslo.messaging 5.0.0. Global requirements for stable/mitaka has oslo.messaging>=4.0.0 so it can fetch 5.0.0.
> Just reminding that it breaks us because we intentionally modified RPCDispatcher like in [1]. It was needed for “at-least-once” delivery. In master we already agreed to remove that hack and work towards having a decent solution (there are options). The patch is [2]. But we need to handle it in mitaka somehow.
> Options I see:
> Constrain oslo.messaging in global-requirements.txt for stable/mitaka with 4.6.1. Hard to do since it requires wide cross-project coordination.
> Remove that hack in stable/mitaka as we did with master. It may be bad because this was wanted very much by some of the users
> Not sure what else we can do.

You could set up your test jobs to use the upper-constraints.txt file in
the requirements repo.

What was the outcome of the discussion about adding the at-least-once
semantics to oslo.messaging?


> Thoughts?
> [1] https://github.com/openstack/mistral/blob/stable/mitaka/mistral/engine/rpc.py#L38-L88 <https://github.com/openstack/mistral/blob/stable/mitaka/mistral/engine/rpc.py#L38-L88>
> [2] https://review.openstack.org/#/c/316578/ <https://review.openstack.org/#/c/316578/>
> Renat Akhmerov
> @Nokia

More information about the OpenStack-dev mailing list