So pip-freeze.txt shows that there was installed oslo.messaging 3.0.0 [1] and if we take a look at it's requirements it can be seen that it requires oslo.service>=0.12.0 while in global-requirements it's pinned at oslo.service>=0.7.0 and oslo.service===1.1.0 in upper-constraints.
At the same time the latest version tag we had in stable/liberty was 0.9.0 so I think that is why there was a version conflict. I don't have enough knowledge of how upper-constraints mechanism works but shouldn't the value in constraints.txt somehow correlate with the latest stable/liberty version?
So pip-freeze.txt shows that there was installed oslo.messaging 3.0.0 [1] and if we take a look at it's requirements it can be seen that it requires oslo.service> =0.12.0 while in global-requirements it's pinned at oslo.service>=0.7.0 and oslo.service= ==1.1.0 in upper-constraints.
At the same time the latest version tag we had in stable/liberty was 0.9.0 so I think that is why there was a version conflict. I don't have enough knowledge of how upper-constraints mechanism works but shouldn't the value in constraints.txt somehow correlate with the latest stable/liberty version?
[1] http:// logs.openstack. org/43/ 256443/ 1/check/ gate-tempest- dsvm-neutron- src-oslo. service/ d3c7268/ logs/pip- freeze. txt.gz /github. com/openstack/ oslo.messaging/ blob/3. 0.0/requirement s.txt#L13
[2] https:/