Bug #1087
Chown operation can leave outdated objects in the cache
| Status: | Closed | Start date: | 01/25/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Release 3.2.1 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.2 |
Description
Because cached objects are indexed by ID and the <name,owner> key, the chown operation must update the name index.
When VM templates use Images or VNets by name, outdated objects (with previous owner) can be accessed with a specific sequence of operations.
Thanks to Akihiko Ota for reporting in the mailing list:
http://lists.opennebula.org/pipermail/users-opennebula.org/2012-January/007666.html
Associated revisions
Bug #1087: Update cache name index after a chown operation
Bug #1087: Update cache name index after a chown operation
(cherry picked from commit def2de2a6838dbbe8dc6c08dcfdeba74944b4068)
bug #1087: More work on the cache
bug #1087: More work on the cache
(cherry picked from commit f05942f6e4b3658ccd3f17226514b2f97683d4c0)
Bug #1087: Core tests
Bug #1087: Core tests
(cherry picked from commit f10e852fe4c693c069026475e36ecd16b6b32d2a)
History
#1
Updated by Carlos Martín over 9 years ago
- Status changed from New to Closed
- Target version set to Release 3.2.1
- Resolution set to fixed