After tempest run, project is not cleaned up, can't delete project in a hierarchy

[Brant Knudson]

After running tempest, there's a project left around.

Here's an example from a recent run: http://logs.openstack.org/95/332495/5/check/gate-tempest-dsvm-full/fcefa16/logs/tempest.txt.gz#_2016-06-22_20_19_22_952

To find in a log, just search the tempest log for ListProjectsTestJSON:tearDownClass.

Request (ListProjectsTestJSON:tearDownClass): 403 DELETE http://127.0.0.1/identity_v2_admin/v3/projects/f30901deac964412a85ecd2dd7074abd 0.147s
...
Details: {u'code': 403, u'message': u'Cannot delete the project f30901deac964412a85ecd2dd7074abd since it is not a leaf in the hierarchy. Use the cascade option if you want to delete a whole subtree.', u'title': u'Forbidden'}

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/333526

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/333526
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=e77b6899594232f1ecadfd752c50005756ebbd5b
Submitter: Jenkins
Branch: master

commit e77b6899594232f1ecadfd752c50005756ebbd5b
Author: Brant Knudson <email address hidden>
Date: Thu Jun 23 13:07:47 2016 -0500

    Cleanup projects in reverse order

    Commit 0a592b4 introduced a change where a hierarchy of projects
    is created. Of course, the parent project is created before the
    child project. The project cleanup code was deleting projects in
    the order that they're created. Keystone doesn't allow deleting the
    parent before the children so this was causing the project to be
    left around (the DELETE operation was failing but cleanup failures
    are ignored).

    The fix here is to do the cleanups in reverse order so that the
    child is deleted before the parent.

    Change-Id: Id7422967ccb666966fbce5a175db5e128b2d3df7
    Closes-Bug: 1595638