I could see that the Unit tests are run against the latest oslo.messaging from the master, and source tree is old. http://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints... oslo.messaging===9.2.1 [root@ip9-114-192-185 cinder-es]# grep install_command tox.ini install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE: https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraint... } {opts} {packages} [root@ip9-114-192-185 cinder-es]# Will get the configuration fixed. Thanks for the clarification. Thanks & Regards, Chhavi Agarwal Cloud System Software Group. From: Sean McGinnis <sean.mcginnis@gmail.com> To: iain.macdonnell@oracle.com Cc: chhagarw@in.ibm.com, openstack@lists.openstack.org, openstack-discuss@lists.openstack.org, jungleboyj@electronicjungle.net, John Griffith <john.griffith8@gmail.com> Date: 11/28/2018 12:39 AM Subject: Re: [Openstack] [Cinder] Cinder New Tag Release On Tue, Nov 27, 2018 at 1:05 PM iain MacDonnell <iain.macdonnell@oracle.com
wrote:
Want to know if we can have a new Cinder tag release to incorporate the new fixes.
[attempting to cross-post to openstack-discuss]
Cinder 13.x releases are OpenStack Rocky, and the upper-constraints for
Rocky [1] says oslo.messaging===8.1.2, so there should be no need to backport this fix.
Are you trying to run the unit tests when you see this? When I run tox on stable/rocky, it installs 8.1.2 as one of the dependencies, although, to be honest, I'm really not sure how tox knows that that's the right version.
Ahh, here's how it knows :- $ grep install_command tox.ini install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE: https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraint... } {opts} {packages} $ ~iain Yeah, we shouldn't need to backport something like this. We have upper constraints specifically to avoid needing to handle cases like this. Sean
