Tests should have caught "Keystone servers fail to start" bug
Bug #903713 reported by
Thierry Carrez
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Invalid
|
High
|
Unassigned | ||
Bug Description
Bug 901453 describes an issue where keystone servers are failing to start in trunk.
The basic problem is that there is clearly a missing "from keystone import version" in keystone/server.py; however, a more serious problem is that this was not caught by the unit tests before merging whatever the responsible patch was with trunk.
| Changed in keystone: | |
| milestone: | none → essex-3 |
| Changed in keystone: | |
| status: | In Progress → Confirmed |
| summary: |
- Unit tests should have caught "Keystone servers fail to start" bug + Tests should have caught "Keystone servers fail to start" bug |
| Changed in keystone: | |
| milestone: | essex-3 → essex-4 |
| Changed in keystone: | |
| assignee: | Dolph Mathews (dolph) → nobody |
| tags: | added: legavy |
| tags: |
added: legacy removed: legavy |
| Changed in keystone: | |
| milestone: | essex-4 → none |
Revision history for this message
| Dolph Mathews (dolph) wrote | #1 |
| Changed in keystone: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
This is essentially "fixed" now that keystone is gated by devstack. However, I'm marking as invalid because I don't think "Fix Released" is appropriate; there has been no associated commit made to keystone.
https:/