-
Notifications
You must be signed in to change notification settings - Fork 101
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
Clean up resources even though AWS resources are not used (bug fix) #4541
Conversation
t.Logf("validating deletion of AWS resource for %s", ct.Description) | ||
validation.ValidateNoAWSResource(ctx, t, &resource, ct.Options.AWSClient) | ||
t.Logf("finished validation of deletion of AWS resource %s for %s", resource.Name, ct.Description) | ||
if step.AWSResources != nil && len(step.AWSResources.Resources) > 0 { |
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.
@vinayada1 I think this is the bug. If there is no AWS resources, then it skips all resource clean up. Please let me know if there is reason we skip the non-aws resource clean up
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.
Yes, this is a bug! Could we change the logic in line 292 as well just in case we end up adding more cleanup after that?
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.
When I fix this, then I do see lots of failures from dapr related functional tests! I cannot merge this until I figure it out the root cause. I will set up the meeting with @vishwahiremat @vinayada1 @kachawla
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.
Do we need to check if step.AWSResources.Resources
is nil?
This reverts commit e525d25.
After this change, I do see lots of failures from dapr related functional tests. I do not see any issues in the other tests. I think we need to look at why it happens before releasing v0.15 - cc/ @vinayada1 @kachawla @vishwahiremat
|
closing with #4612 |
Description
This is the fix to clean up resource even though AWS resources are not used.
Issue reference
Fixes: #issue_number
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: