yahoo-eng-team team mailing list archive

[OpenStack Infra <1731948@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/519622
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5e08a9b0e7d4f99d217ca73c6aa37e52a13c5d5a
Submitter: Zuul
Branch:    master

commit 5e08a9b0e7d4f99d217ca73c6aa37e52a13c5d5a
Author: Sławek Kapłoński <slawek@xxxxxxxxxxxx>
Date:   Tue Nov 14 20:36:39 2017 +0000

    [OVO] Switch to use own registry
    
    Neutron will now use own registry for versionedobjects.
    It avoids problems with loading wrong OVO objects from
    different projects (like os_vif) when names are the same.
    
    Change-Id: I9d4fab591fbe52271c613251321a6d03078976f7
    Closes-Bug: #1731948


** Changed in: neutron
       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/1731948

Title:
  Wrong OVO classes registered in some cases

Status in neutron:
  Fix Released
Status in oslo.versionedobjects:
  New

Bug description:
  When patch https://review.openstack.org/#/c/321001 was merged some UT
  in projects like networking-midonet started failing. It is reported on
  https://bugs.launchpad.net/networking-midonet/+bug/1731623

  It looks that reason of this problem is that wrong OVO classes are
  registered in case when e.g. 2 different projects uses same names of
  OVO objects.

  I checked it little bit and it looks that
  neutron.objects.subnet.Subnet has got registered
  os_vif.objects.route.Route object instead of
  neutron.objects.subnet.Route, see my logs from one exampled test:
  http://paste.openstack.org/show/626170/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1731948/+subscriptions