← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1568708] Re: translation sync broken due to wrong usage of venv

 

Reviewed:  https://review.openstack.org/335527
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=e11be5726a51d4a7a41abb1899a6dcc85691b3e7
Submitter: Jenkins
Branch:    master

commit e11be5726a51d4a7a41abb1899a6dcc85691b3e7
Author: Kyle Mestery <mestery@xxxxxxxxxxx>
Date:   Wed Jun 29 09:23:10 2016 -0500

    tox.ini: Stop using zuul-cloner for venv
    
    This should fix the translation job, similar to the fix for
    networking-midonet [1].
    
    [1] https://review.openstack.org/#/c/330871/
    
    Change-Id: I83f7b41221614e9eb28e2f95bfd11bc54d7d404f
    Closes-Bug: #1568708
    Signed-off-by: Kyle Mestery <mestery@xxxxxxxxxxx>


** Changed in: networking-ovn
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1568708

Title:
  translation sync broken due to wrong usage of venv

Status in networking-midonet:
  Fix Released
Status in networking-ovn:
  Fix Released
Status in neutron:
  Fix Committed
Status in Sahara:
  Fix Released
Status in Sahara mitaka series:
  Fix Released

Bug description:
  post jobs cannot use zuul-cloner and have no access currently to
  upper-constraints. See how nova or neutron itself handle this.

  Right now the sync with translations fails:

  https://jenkins.openstack.org/job/neutron-fwaas-propose-translation-
  update/119/console

  Please fix venv tox environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1568708/+subscriptions


References