trove configuration-update doesn't revert the effect of the previously enforced configuration group before enforcing the new one
Bug #1449238 reported by
Amrith Kumar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
On Kilo-1 ...
a configuration-
See file attached.
Revision history for this message
| Amrith Kumar (amrith) wrote | #1 |
| Changed in trove: | |
| assignee: | nobody → Amrith (amrith) |
| Changed in trove: | |
| status: | New → Confirmed |
| summary: |
- trove configuration-update doesn't + trove configuration-update doesn't revert the effect of the previously + enforced configuration group before enforcing the new one |
| Changed in trove: | |
| milestone: | liberty-1 → liberty-2 |
| Changed in trove: | |
| milestone: | liberty-2 → liberty-3 |
| status: | Confirmed → Triaged |
| Changed in trove: | |
| milestone: | liberty-3 → next |
| Changed in trove: | |
| milestone: | next → liberty-rc1 |
Revision history for this message
| Nikhil Manchanda (slicknik) wrote | #2 |
| Changed in trove: | |
| milestone: | liberty-rc1 → next |
| Changed in trove: | |
| assignee: | Amrith (amrith) → nobody |
To post a comment you must log in.
This fix isn't in progress yet and the Liberty RC1 cut is in a week's time. Given that, and the fact that I don't think this bug is a blocker for Liberty -- moving this bug over to the next release. Thanks!