Bug 1328758 - Autoscaling using AWS Cloud formation template not spinning new instance on termination
Summary: Autoscaling using AWS Cloud formation template not spinning new instance on t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification-openstack
Version: 1.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Rohan Kanade
QA Contact: Anshul Behl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 08:48 UTC by Manish
Modified: 2018-04-26 05:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-26 05:26:40 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1572445 0 None None None 2016-04-20 08:48:41 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.