recordset status not always returning the correct value

Bug #1842994 reported by Erik Olof Gunnar Andersson on 2019-09-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
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

Reviewed: https://review.opendev.org/660503
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=57f420801c9e064c9ff8f1a4ab779e0b67260486
Submitter: Zuul
Branch: master

commit 57f420801c9e064c9ff8f1a4ab779e0b67260486
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: Ic2f4f41a9a87440e3849f380ea5989e15f378619

Changed in designate:
status: In Progress → Fix Released

This issue was fixed in the openstack/designate 9.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers