Bug 1328758

Summary: Autoscaling using AWS Cloud formation template not spinning new instance on termination
Product: Red Hat Certification Program Reporter: Manish <manish.upadhyay>
Component: redhat-certification-openstackAssignee: Rohan Kanade <rkanade>
Status: CLOSED NOTABUG QA Contact: Anshul Behl <abehl>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-26 05:26:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Manish 2016-04-20 08:48:42 UTC 
Description of problem:
Environment: RHEL 7.2
OpenStack Distribution: Liberty.

Scenario:

Want to achieve autoscaling using YAML and AWS Cloud formation template. as a test we have used minsize =1 maxsize=5 desired capcity =3. Autoscaling should be on abrupt termination or based on some alarm (In our case we used same cpu >50%).

All the scenarios working fine with YAML template.

when we use AWS Cloud formation template. It is able to spin new instance on the basis of alarm. However if we abruptly terminate an instance with desired capacity =3 it is not spinning new instance automatically. No errors are getting reported.

If i go to stack and try to see the autoscaling resources i could see the resource (OS::Heat::ScaledResource) related to terminated instance is still there. Also if we perform "check stack" or supend stack it gives below error.

"NotFound: resources.<resource id>: Instance <instance id> could not be found. (HTTP 404) (Request-ID: req-6f112170-5687-43aa-b2d7-16e92d2ae2a2)".

This seems to be a bug.