Domain config management is not thread-safe
Bug #1438617 reported by
Henry Nash
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
The domain configuration management methods use a set on non-atomic operations to store the values in the database. This means that in multi-threaded configurations, a GET might, for instance, return a partial config if it where being modified by another thread at the same time.
Domain configuration management are relatively infrequent operations, but someone, somewhere will fall into this hole.
Revision history for this message
| Morgan Fainberg (mdrnstm) wrote | #1 |
| Changed in keystone: | |
| status: | New → Triaged |
| importance: | Medium → Wishlist |
Revision history for this message
| Steve Martinelli (stevemar) wrote | #2 |
| Changed in keystone: | |
| milestone: | next → none |
| assignee: | Henry Nash (henry-nash) → nobody |
To post a comment you must log in.
Also moving this to wishlist. It is needed for DomainSQL to be stable but isn't super important for someone to pickup