vm_state become error if vm_state is resized and power_state is shutdown

Bug #1782518 reported by Rikimaru Honjo on 2018-07-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

A host-failure was occurred.
There was a instance that was vm_state=resized, power_state=SHUTDOWN.
Masakari tried to recovery it.

As a result, notification status became finished.
But, instance's vm_state became error.

I expected the stopped state.

I used the latest version of masakari.

Changed in masakari:
assignee: nobody → takahara.kengo (takahara.kengo)
takahara.kengo (takahara.kengo) wrote :
Changed in masakari:
status: New → In Progress

Reviewed: https://review.openstack.org/585592
Committed: https://git.openstack.org/cgit/openstack/masakari/commit/?id=c3d12e37b0c5123cb2b2397c12f6f4ba6c45e73f
Submitter: Zuul
Branch: master

commit c3d12e37b0c5123cb2b2397c12f6f4ba6c45e73f
Author: Kengo Takahara <email address hidden>
Date: Wed Jul 25 11:22:54 2018 +0900

    Recover resized instance(power_state=SHUTDOWN) with vm_state=stopped

    The instance which is vm_state=resized and power_state=SHUTDOWN
    should not be recovered with vm_state=error. It should be recovered
    with vm_state=stopped. The instances such as paused or suspended
    (which are other than vm_state=active,stopped,error) are also the same.

    This patch modified that masakari-engine will recover these instances
    with vm_state=stopped.

    Change-Id: Ibdea705f69d139834c9b2294ae11bc9344c259bd
    Closes-Bug: #1782518

Changed in masakari:
status: In Progress → Fix Released

This issue was fixed in the openstack/masakari release candidate.

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

Other bug subscribers