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

[Guangya Liu (Jay Lau)]

"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.

[Thomas Herve (therve)]

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

[Clint Byrum (clint-fewbar)]

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)

[Michał Jastrzębski (inc007)]

This requires convergence observer to happen