-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ec2_asg: enable integration tests, change instance type to a type allowed by policy #815
ec2_asg: enable integration tests, change instance type to a type allowed by policy #815
Conversation
recheck |
1 similar comment
recheck |
@mandar242 Ah, there's a bug in the tests that only happens when the resource_prefix (which is based on the test system hostname) has dashes at the end.
This regex takes whatever the last 8 characters are, without consideration that The resource_prefix in CI looks like: |
8cfba75
to
e2876cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spent some time on the failures for the mixed-instances test but I haven't got it sorted out yet. I suspect it might have something to do with the way AWSServiceRoleForAutoScaling is being used to access the launch template. Documenting what I've tried here:
Changing the compute policy to allow the AllowAsgInstancesInstanceType
Sid to access resource '*'
gets me to a new, more descriptive error that An error occurred (AccessDenied) when calling the UpdateAutoScalingGroup operation: You are not authorized to use launch template: lt-0a2196568c24cb25d",
. I'm not finding a whole lot of documentation for PassRole for ASGs but I took a couple tries at allowing AWSServiceRoleForAutoScaling to be passed to ec2 with no success. I've reverted the CI staging policies back to main in the interim.
@tremble Do you have any experience working with ASG policies and launch templates?
This comment was marked as outdated.
This comment was marked as outdated.
recheck |
This comment was marked as outdated.
This comment was marked as outdated.
recheck |
Build succeeded (third-party-check pipeline).
|
This comment was marked as outdated.
This comment was marked as outdated.
recheck |
This comment was marked as outdated.
This comment was marked as outdated.
recheck |
Build succeeded.
|
and fixed here: Issue: ansible/ansible#28087 PR: https://github.com/ansible/ansible/pull/36679/files This behavior no longer seems to be present with current boto version being used by tests.
Build failed.
|
2016171
to
53f7251
Compare
Build succeeded.
|
thanks @mandar242! good work on this one! |
Build succeeded (gate pipeline).
|
Depends-On: ansible/ansible-zuul-jobs#1247
SUMMARY
Enable ec2_asg integration tests as fix for resolving ec2_asg failing due to policies missing is merged.
Also change the instance type used in couple of assertions to a type which is allowed by the policy to fix failure.
ISSUE TYPE
COMPONENT NAME
ec2_asg