On Aug 14, 2015, at 6:23 AM, Ihar Hrachyshka <ihrachys@...> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/14/2015 12:15 PM, Flavio Fernandes wrote:

On Aug 13, 2015, at 9:04 AM, Ihar Hrachyshka
<ihrachys@... <mailto:ihrachys@...>> wrote:

On 08/13/2015 02:46 PM, Flavio Fernandes wrote:

On Aug 13, 2015, at 8:30 AM, Ihar Hrachyshka
<ihrachys@... <mailto:ihrachys@...>
<mailto:ihrachys@...>> wrote:

Looking at the logs in the email thread:

2015-08-05 14:59:53.160 | Download error on
https://pypi.python.org/simple/pbr/: [Errno 110] Connection
timed out -- Some packages may not be found! 2015-08-05
15:02:00.392 | Download error on
https://pypi.python.org/simple/: [Errno 110] Connection timed
out -- Some packages may not be found! 2015-08-05
15:02:00.392 | No local packages or download links found for
pbr>=1.3

So why can't your machine download the satisfying pbr
version? It's available on pypi, so assuming you fix the
download error, I think it should proceed.

That is the issue. This happens because OFFLINE=True and
there is still something in pbr requirements that is
looking for a version of pbr that is not used in
stable/kilo.

I suspect this is happening because stable/kilo branch in
networking-odl was created ‘late’ and the new version of
pbr was added as part of liberty?!?

So, to easily reproduce this issue: 1) stack with
devstack+networking-odl on stable/kilo; 2) untack; 3)
change OFFLINE=True and 4) attempt to stack again.

Are your repo [test-]requirements.txt synchronized with neutron's
kilo requirements? They should, otherwise it won't be ever
supported.

They do not for requirements.txt:

$ diff requirements.txt.neutron requirements.txt.networking-odl |
grep pbr < pbr!=0.7,<1.0,>=0.6

pbr<2.0,>=1.3

$ diff test-requirements.txt.neutron
test-requirements.txt.networking-odl | grep pbr $

So that's a problem. You don't even have a common pbr version that
would satisfy both projects.

If you look closely, that is what is changed in the abandoned
gerrit [1]. Maybe the right thing to do is to re-visit that
gerrit and make sure the requirement.txt files are inline?!?

The fix is obvious: make stable/kilo requirements in your repo
synchronized with what is in stable/kilo for neutron. Same for all
other branches.

Openstack requirements proposal bot can help you maintain the lists
synchronized. To make sure your repo gets updates from the bot, add it
in projects.txt in openstack/requirements repo (in master and in
stable/kilo).

Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVzcGQAAoJEC5aWaUY1u5702IIAOEyOi+/3SLXw8DW7Dl2q16g
b2RS/F9X6004cAOcKT6L+12g6+R3OuRUaT4WlsH1BzFfLV3pakGAgRR2cAxyYlHw
dbbsAvm7lXNTAGGS/ep9xujAwhNTr0eQ3ZEcR3THHjcoThEPYP27Ha2zEdSYyzV9
sArzcDHQTjcV2JwAdaT1GmVxlviJjrxt2jvSXATck0MxPzwmDLhrEAnZ+M17K0bQ
nRO3A650/xo5AJmwT2vNG5wi+/cC9LtjinInrrN8CK2abQB8L2NYrucv3gDRG3FI
xT1nAjP6HgDzKeyLESWgZgXS2njoOZZo7rc4ejd55w0TXKEYn/rdKONpHsN3iRI=
=9y75
-----END PGP SIGNATURE-----