Tempest assumes project_id is meaningful in Nova tests
Bug #1506037 reported by
Sean Dague
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Opinion
|
Undecided
|
Unassigned |
Bug Description
When trying to remove project_id from Nova urls, there are a few tempest tests that fail because they assume project_id in the url is meaningful to Nova (it's not).
These tests attempt to create a value under a different tenant by changing the url. If we make project_id optional in Nova, these calls no longer fail, but they don't create the entity under the new tenant (which is what the Tempest tests are trying to do).
Exactly how we rescope these tests at this point is unclear, but it does inhibit our ability to provide a migration path to a non project_id url world.
To post a comment you must log in.
I think this is a related patch for this bug. And is this still an actual bug? 48ce95a988c43cc 9affe50652
------------
commit a0a9b24de0a2b2c
Author: Sean Dague <email address hidden>
Date: Wed Mar 30 07:42:08 2016 -0400
Remove AuthorizationTe stJSON tests
These are a set of legacy negative tests that make an assumption that
Nova service URLs will have {project_id} in them, and that changing
the value of {project_id} is a meaningful way to attempt to access
resources by another tenant. Neither of these things are true.
As of midway through Mitaka Nova landed a microversion that makes
{project_id} an optional construct. When we actually deploy systems
with this, of the 25 tests listed, 20 fail, 3 are skipped (due to
custom skip logic I previously add), and 2 pass. Those 2 passes are
actually as suspect as anything else, as they should now fail, and
demonstrates other bugs in Tempest.
The removal of these tests followed the full process required for lists.openstack .org/pipermail/ openstack- dev/2016- March/088716. html
removal of tests -
http://
Change-Id: I81d99d65b8affa ea44ddd6643d6ac c40068eead7
------------