Closed sjones4 closed 3 years ago
ELBv2 target health checks for AutoScaling.
Build: https://dev.azure.com/corymbia/eucalyptus/_build/results?buildId=1315 Test: https://dev.azure.com/corymbia/eucalyptus/_build/results?buildId=1316
Tested by manually updating the health state of a target in the load balancer database to cause a health check failure and verifying the instance was replaced in the autoscaling group:
# euscale-describe-auto-scaling-groups AUTO-SCALING-GROUP elbv2-as-1-AutoScalingGroup-QTXDRFZ7BQITA elbv2-as-1-LaunchConfiguration-3TRY9SGEYZVIW cloud-1a 0 1 1 Default INSTANCE i-75e623770e485b769 cloud-1a Pending Healthy elbv2-as-1-LaunchConfiguration-3TRY9SGEYZVIW TAG auto-scaling-group elbv2-as-1-AutoScalingGroup-QTXDRFZ7BQITA aws:cloudformation:logical-id AutoScalingGroup true TAG auto-scaling-group elbv2-as-1-AutoScalingGroup-QTXDRFZ7BQITA aws:cloudformation:stack-id arn:aws:cloudformation::000714107038:stack/elbv2-as-1/e6af597e-0a4c-47c2-bb56-49fa714bd16b true TAG auto-scaling-group elbv2-as-1-AutoScalingGroup-QTXDRFZ7BQITA aws:cloudformation:stack-name elbv2-as-1 true
Relates to corymbia/eucalyptus#271
ELBv2 target health checks for AutoScaling.
Build: https://dev.azure.com/corymbia/eucalyptus/_build/results?buildId=1315 Test: https://dev.azure.com/corymbia/eucalyptus/_build/results?buildId=1316
Tested by manually updating the health state of a target in the load balancer database to cause a health check failure and verifying the instance was replaced in the autoscaling group:
Relates to corymbia/eucalyptus#271