Node stop is not called before deletion

Bug #1816677 reported by Duc Truong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
senlin
Fix Released
Undecided
Unassigned

Bug Description

1. Create cluster with 2 nodes. One of the node failed to create and its physical id is None
2. Scale in cluster with step size 2
3. First node will not enter wait for lifecycle completion because its physical id is None

Expected Results:
Second node is stopped and then deleted.

Actual Results:
Stop is never called for second node. The stop operation is stuck in INIT and eventually fails due to timeout. Then node delete is called

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to senlin (master)

Reviewed: https://review.openstack.org/638035
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=3e70333a65dd168c2c4a4d8839d2980e54152697
Submitter: Zuul
Branch: master

commit 3e70333a65dd168c2c4a4d8839d2980e54152697
Author: Duc Truong <email address hidden>
Date: Tue Feb 19 22:38:51 2019 +0000

    Fix node delete with lifecycle hook bug

    Create copy of child node list and remove nodes from the original child
    list if a node does not need to enter waiting lifecycle completion
    because it is not found or not in ACTIVE state.

    Change-Id: I04d57f4deb2f9f46aba1d9d4a566cb90dbe74d96
    Closes-Bug: #1816677

Changed in senlin:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/senlin 7.0.0.0b1

This issue was fixed in the openstack/senlin 7.0.0.0b1 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.