heat autoscale scale up does not work if delete one instance manually

Bug #1260167 reported by Guangya Liu (Jay Lau)
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
Anant Patil

Bug Description

"WebServerGroup" : {
      "Type" : "AWS::AutoScaling::AutoScalingGroup",
      "Properties" : {
        "AvailabilityZones" : { "Fn::GetAZs" : ""},
        "LaunchConfigurationName" : { "Ref" : "LaunchConfig" },
        "MinSize" : "1",
        "MaxSize" : "2"

Then when the WebServerGroup reach MaxSize 2, delete one instance manually. Then WebServerGroup never scale up and the instance number in WebServerGroup keeps in 1.

The expected behavior should be the autoscaling policy scale up the instance number to 2 again.

Revision history for this message
Thomas Herve (therve) wrote :

That's an issue indeed. There is no simple solution though, apart from implementing a convergence mechanism.

Changed in heat:
assignee: nobody → Alexander Chudnovets (achudnovets)
Changed in heat:
assignee: Alexander Chudnovets (achudnovets) → nobody
lvdongbing (dbcocle)
Changed in heat:
assignee: nobody → lvdongbing (dbcocle)
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

lvdongbing, do you have a patch in-progress? If not, I would suggest that you leave this bug unassigned so that the next available developer can take it (also consider that convergence may make this bug obsolete, see https://blueprints.launchpad.net/heat/+spec/stack-convergence)

Changed in heat:
status: New → Confirmed
importance: Undecided → Medium
lvdongbing (dbcocle)
Changed in heat:
assignee: lvdongbing (dbcocle) → nobody
Angus Salkeld (asalkeld)
tags: added: autoscaling
Revision history for this message
Michał Jastrzębski (inc007) wrote :

This requires convergence observer to happen

Anant Patil (ananta)
Changed in heat:
assignee: nobody → Anant Patil (ananta)
tags: added: fixed-by-convergence
Changed in heat:
status: Confirmed → Triaged
Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
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.