senlin

LB policy is not working in a correct way

Bug #1530746 reported by Qiming Teng on 2016-01-04

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	senlin	Fix Released	Critical	Yanyan Hu	senlin mitaka-2 "m2"

Bug Description

Currently the load balancing policy is detaching nodes from the load-balancer *after* nodes are deleted. This is wrong. We should detach nodes from the load-balancer *before* the nodes are deleted.

Revision history for this message

Yanyan Hu (yanyanhu) wrote on 2016-01-05:

Yes, detaching lb member from loadbalancer before corresponding node is deleted is the correct logic. The problem is in some cases, we don't know which node(s) will be deleted before the action is executed, e.g. resize cluster with random victim choosing. So I guess we may need to eliminate those random deleting logic before fix this problem. Will think about it.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-01-05: Fix proposed to senlin (master)

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

Changed in senlin:
status:	Triaged → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-01-06: Fix merged to senlin (master)

Reviewed: https://review.openstack.org/263631
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=84b39d1eb718df74503c07c84d7e0853ef8dc70b
Submitter: Jenkins
Branch: master

commit 84b39d1eb718df74503c07c84d7e0853ef8dc70b
Author: yanyanhu <email address hidden>
Date: Tue Jan 5 03:07:31 2016 -0500

Set cluster to correct status when scaling failed

    Currently, cluster status will not be set to correct value when
    resizing/scaling action failed for size limitation check failure.
    This patch fixes this issue.

Change-Id: I9de9a8684c8aa6ffeae9b5f7df9331e51eb168b3
Closes-Bug: #1530746