Unit tests use inconsistent default tenant id

Bug #1335821 reported by Assaf Muller
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Assaf Muller

Bug Description

Meters and security groups use 'test_tenant' while all other resources use 'test-tenant'.

This means that a test that creates multiple types of resources (While using the the default tenant id) would find that some resources were created under one tenant, and other resources under another tenant.

For example, a test creates a network, subnet, port, security group and meter label + rule. Listing all resources that belong to the 'test-tenant' would return a partial list, leading to confusing results.

Tags: unittest
Assaf Muller (amuller)
Changed in neutron:
assignee: nobody → Assaf Muller (amuller)
Changed in neutron:
status: New → In Progress
Changed in neutron:
importance: Undecided → Low
milestone: none → juno-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/91961
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5b34d41828a2a1260b1b92f6bfd91e1264aea7a8
Submitter: Jenkins
Branch: master

commit 5b34d41828a2a1260b1b92f6bfd91e1264aea7a8
Author: Assaf Muller <email address hidden>
Date: Sat May 3 17:05:04 2014 +0300

    Replace occurences of 'test_tenant' with 'test-tenant' in tests

    tenant_id will now be consistent among all resources created.
    This is important when getting or listing resources by tenant_id.
    Most resources are created under the 'test-tenant', while
    metering and security groups were created under 'test_tenant'.

    Closes-Bug: #1335821
    Change-Id: Ifde22814ab5c302e751f2102f6fd7ef52c932126

Changed in neutron:
status: In Progress → Fix Committed
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: juno-2 → 2014.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.