Open Stack

Hi Előd,

Thanks for looking into that.

Summary:
- we  removed networking-odl from required-projects of networking-bgpvpn 
because of a history of networking-odl changes breaking functional tests 
in networking-bgvpn
(since networking-bgpvpn master declares networking-odl in 
requirements.txt , the tox-siblings magic would prevent us from pinning 
our networking-odl dep to a pypi release)
- the side effect, as you identified, is that this breaks stable/* 
branches of networking-bgpvpn, which still use toos/tox_install.sh (and 
can't stop doing so because in stable branches, the requirement checking 
job still prevents the addition of networking-odl in requirements.txt)

I think that, if doable, it would be nice to avoid complexifying the 
zuul job configuration to keep networking-odl.
If it can't be avoided then something like your change  [3] would be the 
way, I guess.

Andreas, Monty, any guidance ?

-Thomas

[3] https://review.openstack.org/#/c/572495/



On 06/06/2018 13:28, Elõd Illés wrote:
> Hi,
>
> I'm trying to create a fix for the failing networking-bgpvpn stable 
> periodic sphinx-docs job [1], but meanwhile it turned out that other 
> "check" (and possibly "gate") jobs are failing on stable, too, on 
> networking-bgpvpn, because of missing dependency: networking-odl 
> repository (for pep8, py27, py35, cover and even sphinx, too). I 
> submitted a patch a couple of days ago for the stable periodic py27 
> job [2] and it solved the issue there. But now it seems that every 
> other networking-bgpvpn job needs this fix if it is run against stable 
> branches (something like in this patch [3]).
>
> Question: Is there a better way to fix these issues?
>
>
> The common error message of the failing jobs:
> **********************************
> ERROR! /home/zuul/src/git.openstack.org/openstack/networking-odl not 
> found
> In Zuul v3 all repositories used need to be declared
> in the 'required-projects' parameter on the job.
> To fix this issue, add:
>
>   openstack/networking-odl
>
> to 'required-projects'.
>
> While you're at it, it's worth noting that zuul-cloner itself
> is deprecated and this shim is only present for transition
> purposes. Start thinking about how to rework job content to
> just use the git repos that zuul will place into
> /home/zuul/src/git.openstack.org directly.
> **********************************
>
>
> [1] https://review.openstack.org/#/c/572368/
> [2] https://review.openstack.org/#/c/569111/
> [3] https://review.openstack.org/#/c/572495/
>
>
> Thanks,
>
> Előd
>
>
> __________________________________________________________________________ 
>
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.