Project

General

Profile

Actions

Bug #10018

open

deleting hosts in the aws compute provider doesnt always execute termination on AWS

Added by Brian Galura almost 9 years ago. Updated almost 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - EC2
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

when deleting multiple hosts simultaneously hosts are removed from foreman but not AWS.

in 1.7.1

Actions #1

Updated by Brian Galura almost 9 years ago

Im adding a hook to work around this:
case "$HOOK_EVENT" in
create)
echolog no action for create
;;
destroy)
echolog waiting for instance to be terminated
while [ ! aws ec2 describe-instances --instance-ids $instanceid| grep -q terminated ]
do
echolog waiting for $instanceid to terminate
sleep 10
echolog retrying termination
echolog running aws ec2 terminate-instances --instance-ids $instanceid
aws ec2 terminate-instances --instance-ids $instanceid
done
echolog instance $instanceid now shows as terminated
;;
update)
echolog no action for update
;;
*)
echo "Usage: run_hooks {create|destroy|update}"
exit 1
;;
esac

Actions #2

Updated by Dominic Cleal almost 9 years ago

  • Category set to Compute resources - EC2
  • translation missing: en.field_release deleted (40)

By simultaneously, do you mean using the tickboxes and select action dropdown, or with multiple tabs/windows?

Actions #3

Updated by Brian Galura almost 9 years ago

Dominic Cleal wrote:

By simultaneously, do you mean using the tickboxes and select action dropdown, or with multiple tabs/windows?

I have been using api v2.

Actions

Also available in: Atom PDF