Blazar

Delete host error causes inconsistency

Bug #1721456 reported by Hiroaki Kobayashi on 2017-10-05

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Blazar	Fix Released	High	Hiroaki Kobayashi	Blazar queens-2 "q-2"

Bug Description

When try to delete a host which is reserved for some not-started leases, it fails but the host is removed from the freepool. It means there is still a host in the computehosts table but is not in the freepool. This inconsistency have to be solved.

Hiroaki Kobayashi (hiro-kobayashi) on 2017-10-05

Changed in blazar:
importance:	Undecided → High
milestone:	none → 0.4.0
assignee:	nobody → Hiroaki Kobayashi (hiro-kobayashi)

Hiroaki Kobayashi (hiro-kobayashi) on 2017-10-06

Changed in blazar:
status:	New → Triaged

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-10-06: Fix proposed to blazar (master)

Fix proposed to branch: master
Review: https://review.openstack.org/509953

Changed in blazar:
status:	Triaged → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-10-27: Fix merged to blazar (master)

Reviewed: https://review.openstack.org/509953
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=86101b022fc61c58a77cf975da528c5e78d8eeb4
Submitter: Zuul
Branch: master

commit 86101b022fc61c58a77cf975da528c5e78d8eeb4
Author: Hiroaki Kobayashi <email address hidden>
Date: Fri Oct 6 10:23:18 2017 +0900

Check if a host is reserved before deleting it

    Currently, if you try to delete a host which is reserved, it is removed
    from the freepool but remains in the computehosts table. This patch
    checks if the host is reserved before removing it.

Change-Id: I3daaba338809375e16018ae5e03107d938e89b9c
Closes-Bug: #1721456