yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1731948@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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/

** Affects: neutron
     Importance: Medium
         Status: New

** Project changed: networking-midonet => neutron

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

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