incorrect batch count for rolling update

Bug #1388695 reported by huangtianhua
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
huangtianhua

Bug Description

When try rolling update for autoscaling group, the capacity should be effective_capacity while validating whether the updation will resul in stack update timeout .

Changed in heat:
assignee: nobody → huangtianhua (huangtianhua)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

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

Changed in heat:
status: New → In Progress
Angus Salkeld (asalkeld)
Changed in heat:
importance: Undecided → Medium
milestone: none → kilo-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/132516
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=2edded25b216e0c160b6c2b60e1c95d0ddc29b08
Submitter: Jenkins
Branch: master

commit 2edded25b216e0c160b6c2b60e1c95d0ddc29b08
Author: huangtianhua <email address hidden>
Date: Mon Nov 3 15:27:44 2014 +0800

    Correct validation for timeout when rolling update

    Using effective capacity not the current capacity to calculate
    whether the update action will in result timeout.

    Change-Id: I718e19c197efa5ca3add270a7470ed26e0f705db
    Closes-Bug: #1388695

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: kilo-1 → 2015.1.0
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.