← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1731948] Re: Wrong OVO classes registered in some cases

 

Added oslo.versionedobjects to the list of affected projects so that it
allows to use custom registries for consuming projects.

** Also affects: oslo.versionedobjects
   Importance: Undecided
       Status: New

** Changed in: oslo.versionedobjects
   Importance: Undecided => Wishlist

** Tags added: gate-failure unittest

** Changed in: neutron
   Importance: Medium => High

-- 
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:
  In Progress
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


References