Devstack failure “Oslo.concurrency”
Hello I’m trying to rebuild a Devstack system on an identical machine to a working system from August. Same base OS (Centos 7.5), same simple local.conf. But this system is failing with Oslo.concurrency not at 2.26. This is bizarre because when I update Oslo.concurrency using pip, I’m given 2.29. Yet something in Devstack insists on going back to 2.25.1 despite knowing that I need 2.26. What is most annoying is that I thought that by keeping all the basic build identical I would save myself the pain that is OpenStack installation. How do I work around this please? If I clear out /usr/lib/python2.7/site-packages, this doesn’t seem to help at all. Thanks David Sent from my iPhone
"d.lake@surrey.ac.uk" <d.lake@surrey.ac.uk> writes:
Hello
I’m trying to rebuild a Devstack system on an identical machine to a working system from August.
Same base OS (Centos 7.5), same simple local.conf.
But this system is failing with Oslo.concurrency not at 2.26.
This is bizarre because when I update Oslo.concurrency using pip, I’m given 2.29.
Yet something in Devstack insists on going back to 2.25.1 despite knowing that I need 2.26.
Devstack runs pip using the constraints file to restrict the versions of packages installed to those known to have worked in CI. When you run pip by itself, those constraints are not applied and the newer version is used. Does the error message tell you which package depends on 2.25.1? Why do you need 2.26.0?
What is most annoying is that I thought that by keeping all the basic build identical I would save myself the pain that is OpenStack installation.
How do I work around this please?
If I clear out /usr/lib/python2.7/site-packages, this doesn’t seem to help at all.
Thanks
David
Sent from my iPhone
-- Doug
Hi Doug I cleared that error by recloning Devstack and recompiling. But now I am hitting another issue with trying to set the ip mtu on br-ex which is failing... Have just posted a second email. Thanks David -----Original Message----- From: Doug Hellmann <doug@doughellmann.com> Sent: 19 December 2018 15:29 To: Lake, David (PG/R - Elec Electronic Eng) <d.lake@surrey.ac.uk>; openstack@lists.openstack.org Subject: Re: Devstack failure “Oslo.concurrency” "d.lake@surrey.ac.uk" <d.lake@surrey.ac.uk> writes:
Hello
I’m trying to rebuild a Devstack system on an identical machine to a working system from August.
Same base OS (Centos 7.5), same simple local.conf.
But this system is failing with Oslo.concurrency not at 2.26.
This is bizarre because when I update Oslo.concurrency using pip, I’m given 2.29.
Yet something in Devstack insists on going back to 2.25.1 despite knowing that I need 2.26.
Devstack runs pip using the constraints file to restrict the versions of packages installed to those known to have worked in CI. When you run pip by itself, those constraints are not applied and the newer version is used. Does the error message tell you which package depends on 2.25.1? Why do you need 2.26.0?
What is most annoying is that I thought that by keeping all the basic build identical I would save myself the pain that is OpenStack installation.
How do I work around this please?
If I clear out /usr/lib/python2.7/site-packages, this doesn’t seem to help at all.
Thanks
David
Sent from my iPhone
-- Doug
Quick note: There are no 2.2X releases of oslo.concurrency. It looks like we're probably talking about 3.2X. On 12/19/18 9:28 AM, Doug Hellmann wrote:
"d.lake@surrey.ac.uk" <d.lake@surrey.ac.uk> writes:
Hello
I’m trying to rebuild a Devstack system on an identical machine to a working system from August.
Same base OS (Centos 7.5), same simple local.conf.
But this system is failing with Oslo.concurrency not at 2.26.
This is bizarre because when I update Oslo.concurrency using pip, I’m given 2.29.
Yet something in Devstack insists on going back to 2.25.1 despite knowing that I need 2.26.
Devstack runs pip using the constraints file to restrict the versions of packages installed to those known to have worked in CI. When you run pip by itself, those constraints are not applied and the newer version is used.
Does the error message tell you which package depends on 2.25.1?
Why do you need 2.26.0
Glancing at the current requirements I would guess it's because a lot of services are requiring 3.26: http://codesearch.openstack.org/?q=oslo.concurrency&i=nope&files=requirements.txt&repos= Maybe there's a mismatch with the requirements repo that is capping it at 3.25.1 when some of the other repos moved on to requiring 3.26?
What is most annoying is that I thought that by keeping all the basic build identical I would save myself the pain that is OpenStack installation.
How do I work around this please?
If I clear out /usr/lib/python2.7/site-packages, this doesn’t seem to help at all.
Thanks
David
Sent from my iPhone
participants (3)
-
Ben Nemec
-
d.lake＠surrey.ac.uk
-
Doug Hellmann