Absolute value of input count should be used for cluster scaling
Bug #1449823 reported by
Yanyan Hu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| senlin |
Fix Released
|
High
|
Yanyan Hu | ||
Bug Description
We should use absolute value of input count if it is provided directly with webhook triggering. Otherwise the scalein logic won't work correctly when no ScalingPolicy is attached to cluster.
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to senlin (master) | #1 |
| Changed in senlin: | |
| status: | New → Fix Committed |
| Changed in senlin: | |
| importance: | Undecided → High |
| assignee: | nobody → Yanyan Hu (yanyanhu) |
| status: | Fix Committed → Fix Released |
| milestone: | none → mitaka-2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 858bf54caa4b4e2
Author: yanyanhu <email address hidden>
Date: Tue Apr 28 22:59:31 2015 -0400
Use absolute value of input count for cluster scalein
This patch uses absolute value of input count for cluster scalingin
if it is provided directly with webhook triggering. This makes the
scalein logic work correctly when no ScalingPolicy is attched to
the cluster.
Closes-Bug: #1449823
Change-Id: I05cb9e3f576a89