OpenStack Compute (Nova)

network_info is generated/used haphazardly throughout tests

Reported by Trey Morris on 2011-08-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Wishlist
Trey Morris

Bug Description

It so happens that many of the virt layer tests pass around and receive network_info. This network_info is arbitrarily hardcoded on the spot and then run through the tests. The problem is these hardcoded "network_info"s are not necessarily accurate, and if the format of network_info changes, the tests will continue to use incorrect values which will cause false positive results in our testing framework.

Related branches

lp:~tr3buchet/nova/lp822998
Merged into lp:~hudson-openstack/nova/trunk at revision 1544
Alex Meade (community): Approve on 2011-09-08
Rick Harris (community): Approve on 2011-09-02
Devin Carlen (community): Approve on 2011-09-01
Trey Morris (tr3buchet) on 2011-08-08
Changed in nova:
assignee: nobody → Trey Morris (tr3buchet)
Thierry Carrez (ttx) on 2011-08-11
Changed in nova:
importance: Undecided → Wishlist
status: New → Confirmed
Thierry Carrez (ttx) on 2011-09-05
Changed in nova:
status: Confirmed → In Progress

For some of the tests that are coming for libvirt
(lp:~soren/nova/virt-test-improvements) I add a tests/utils.py that
generates a network_info "object" for my tests. I'm hoping we'll --
over time -- rework all tests to use the same method for generating
network_info objects so that we only have one of these to keep that
up-to-date.

Thierry Carrez (ttx) on 2011-09-20
Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2011-11-09
Changed in nova:
milestone: none → essex-1
Thierry Carrez (ttx) on 2011-11-17
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers