Bug 1372772 - Automate Method: Amazon check_pre_retirement stuck in retry loop
Summary: Automate Method: Amazon check_pre_retirement stuck in retry loop
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: 5.6.5
Assignee: mkanoor
QA Contact: Mike Shriver
URL:
Whiteboard: retirement:ec2
Depends On: 1353632 1378039
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 15:33 UTC by Satoe Imaishi
Modified: 2017-03-13 16:27 UTC (History)
8 users (show)

Fixed In Version: 5.6.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1353632
Environment:
Last Closed: 2017-03-13 16:27:35 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
instance store (160.26 KB, image/png)
2016-11-16 13:29 UTC, Kyrylo Zvyagintsev
no flags Details
set tags (123.39 KB, image/png)
2016-12-20 21:43 UTC, mkanoor
no flags Details

Comment 2 Satoe Imaishi 2016-09-02 15:34:01 UTC
This was fixed in 5.6.1. Please move to CLOSED CURRENTRELEASE if verification passes.

Comment 4 Kyrylo Zvyagintsev 2016-11-16 13:29:43 UTC
Created attachment 1221152 [details]
instance store

Comment 5 mkanoor 2016-12-20 21:43:11 UTC
For instances provisioned outside of CFME you have to set Lifecycle tags.
Without the tags set we will leave the instances around, all we would do is power it off.

For EBS store instances we can power them off
for instance store instances we cannot power them off, since they only allow for termination.

So once you have a VM provisioned outside of CFME

(1) Select the instance
(2) Click on Policy -> Edit Tags
(3) Category -> LifeCycle Assigned Value -> Fully Retire VM and remove from Provider
(4) Save
(5) Then Retire

I have attached a screenshot

Comment 6 mkanoor 2016-12-20 21:43:57 UTC
Created attachment 1234085 [details]
set tags

Comment 7 mkanoor 2017-01-03 16:08:40 UTC
Hello Kyrylo Zvyagintsev,
Does this resolve your issue, if its an instance provisioned outside of CFME it would have to be tagged like mentioned above to finish the retirement.

Thanks,
Madhu

Comment 8 Dave Johnson 2017-02-09 22:33:49 UTC
Mike, can you take a look at this one as it relates to retirement and see if you can reproduce it.  Thanks,  reach out to Milan or Madhu if something is too mysterious, namely automate.  :)

Comment 9 Mike Shriver 2017-03-13 16:27:35 UTC
Tested in CFME 5.6.4.0 and 5.6.3.3

Instance-store backed instances are only powered down (terminated) on EC2 if the appropriate lifecycle tag is assigned. Without this tag the instance is retired in CFME and is left running on the provider.

The retirement process proceeds correctly for both ebs and instance-store type instances, depending on the tags set.


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