Closed anjo-swe closed 2 years ago
Files identified in the description:
plugins/modules/ec2_asg.py
](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/ec2_asg.py)If these files are inaccurate, please update the component name
section of the description or use the !component
bot command.
cc @garethr @jillr @markuman @s-hertel @tremble click here for bot help
Hi @anjo-swe , thank you for reporting this.
You still seem to be on collection version 2.2.0
for community.aws
, with the latest version of community.aws
the issue does not seem to be present.
Could you please upgrade (https://docs.ansible.com/ansible/latest/galaxy/user_guide.html#installing-a-collection-from-galaxy) the community.aws
version and check if the issue still persist?
Thanks!
@anjo-swe
Based on @mandar242's comment I believe this issue has been fixed in recent releases. As such I'm going to close it. If you're still experiencing this issue with the latest releases, feel free to reopen the issue.
Summary
When the ec2_asg module tries to switch an ASG from EC2 to ELB health check type it fails because it expects the instances to be part of the ELB and healthy before it can complete the deploy.
Copied https://github.com/ansible/ansible/issues/55884
Issue Type
Bug Report
Component Name
ec2_asg
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
N/A
Steps to Reproduce
Create an AWS ASG with health check type set to EC2. Then use ansible to change ASG from EC2 to ELB health check.
Expected Results
The AWS ASG to switch from EC2 health check type to ELB health check type.
Actual Results
The ec2_asg call fails because the instances in the ASG are not in the ELB and the call to check instance health fails. This results in the
elb_healthy
andtg_healthy
calls returning None.wait_for_elb
tries to compare the results with the min cluster size and because it cannot compare None and Int with < operator.Code of Conduct