recordset status not always returning the correct value
Bug #1842994 reported by
Erik Olof Gunnar Andersson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
Fix Released
|
Undecided
|
Erik Olof Gunnar Andersson | ||
Bug Description
Depending on the order and status of records in a recordset. There are circumstances where the recordset might report its status as pending, when it should be reporting error.
A recordset should always report its highest priority state when it
contains multiple records. The order of priority is,
`ERROR`, `PENDING`, `ACTIVE` and `DELETED`.
| description: | updated |
| description: | updated |
| description: | updated |
| Changed in designate: | |
| assignee: | nobody → Erik Olof Gunnar Andersson (eandersson) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to designate (master) | #1 |
| Changed in designate: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/designate 9.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 57f420801c9e064
Author: Erik Olof Gunnar Andersson <email address hidden>
Date: Tue May 21 12:55:13 2019 -0700
Fix bug in recordset status
This patch changes the status handling of record sets
to always report the appropriate status.
Closes-Bug: #1842994
Change-Id: Ic2f4f41a9a8744