pxc cluster should error the cluster if the nova instances goto error

Bug #1516763 reported by Craig Vyvial
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Medium
Yao Wang

Bug Description

The pxc cluster stays in a BUILDING task even if the nova instances go straight to error until the cluster building poll times out. Usually the cluster build time out is about 5-10 minutes.

We are polling only the service status and we should also look at the instances status.
https://github.com/openstack/trove/blob/master/trove/taskmanager/models.py#L203-L224

This may also apply to the other clustered datastores as well.

Tags: clusters
Craig Vyvial (cp16net)
Changed in trove:
importance: Undecided → Medium
tags: added: clusters
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

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

Changed in trove:
assignee: nobody → Yao Wang (nihaome521)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/518639
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=d7286833e1cbd7b1263f97ed38c8606fd6437904
Submitter: Zuul
Branch: master

commit d7286833e1cbd7b1263f97ed38c8606fd6437904
Author: wangyao <email address hidden>
Date: Thu Nov 9 09:37:20 2017 +0800

    Stop polling if nova instances goto error

    According bug description, if the nova instances goto error, the cluster
    building poll still work until timeout. To solve this problem, instance
    task status was added in the cluster building poll detection.
    Also provide a test case to validate the method.

    Change-Id: Id772d5528c93fcd061aa9d2b2e56c89229ad655c
    Closes-Bug: #1516763

Changed in trove:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/trove 9.0.0.0b3

This issue was fixed in the openstack/trove 9.0.0.0b3 development milestone.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.