KVS backend fails to update tenants
Bug #954673 reported by
Dolph Mathews
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Dolph Mathews |
Bug Description
In the KVS backend, update_tenant appears to load the existing tenant, and then save it again without considering the input (updated values). It then returns the update data without considering existing data.
This can be reproduced by running the keystone server using the KVS backend, and using the client to create a tenant, update it, and then retrieving (get or list) that tenant again.
The SQL backend appears to perform as expected.
Changed in keystone: | |
status: | Confirmed → In Progress |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/5291 github. com/openstack/ keystone/ commit/ dc41cb5c11951b4 16d3e379bc944ac 85737b979a
Committed: http://
Submitter: Jenkins
Branch: master
commit dc41cb5c11951b4 16d3e379bc944ac 85737b979a
Author: Dolph Mathews <email address hidden>
Date: Tue Mar 13 16:11:27 2012 -0500
Failing to update tenants (bug 953678, bug 954673)
- GET /tenants: Enabled attribute was being overridden {tenant_ id}: was failing to update KVS
- "POST" /tenants/
Change-Id: Icc1efef52d3577 7d73e6010bdfc04 09e24570aa2