keystone user with non existing default tenant

Bug #1453089 reported by Anton Arefiev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
Medium
MOS Keystone

Bug Description

It is possible to create new keystone user with default tenant, but after tenant was deleted user continue contain info about non existing tenant.

Step to reproduce:

1. keystone tenant-create --name ten
     'ten' created successfully

2. keystone user-create --name user --tenant ten
    user created successfully with 'ten' tenantId

3. keystone tenant-delete ten

4. keystone user-get user
    show non existing tenantId

5. keystone tenant-get 'tenant-id'
No tenant with a name or ID of 'tenant-id' exists.

Anton Arefiev (aarefiev)
Changed in mos:
assignee: nobody → MOS Keystone (mos-keystone)
Changed in mos:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 7.0
Revision history for this message
Boris Bobrov (bbobrov) wrote :

The problem is that no resources are cleaned up after a tenant gets deleted. There were upstream discussions about how to address this and AFAIR no decision was made in Kilo.

We are in SCF now, this bug will not be fixed in 7.0. It needs to be reproduced in 8.0 (Liberty).

Changed in mos:
milestone: 7.0 → 8.0
Revision history for this message
Alexander Makarov (amakarov) wrote :

Looks the same for openstack client using v3 API

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :
Changed in mos:
status: Confirmed → Won't Fix
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.