Skip to content
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 #4612

Merged
merged 12 commits into from
Nov 11, 2022

Conversation

youngbupark
Copy link

@youngbupark youngbupark commented Nov 10, 2022

Description

The root cause is the bug in DELETE controller of Dapr resource. As a workaround, this PR skips the resource deletion during tearing down the test.

  • CoreRP resource teardown step has been skipped since 0.14.0 release.
  • Test secret creation and deletion had been removed, which resulted in dapr secret test failures.
  • Changing test concurrency to 1 since local tests without concurrent tests are passing.

Issue reference

Fixes: #4543

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Adds necessary unit tests for change
  • Adds necessary E2E tests for change
  • Unit tests passing
  • Extended the documentation / Created issue for it

@youngbupark youngbupark requested a review from a team as a code owner November 10, 2022 22:08
build/test.mk Outdated Show resolved Hide resolved
@@ -207,12 +207,18 @@ func (ct CoreRPTest) Test(t *testing.T) {
}
})

t.Logf("Creating secrets if provided")
Copy link
Author

@youngbupark youngbupark Nov 10, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol.. this code had been deleted for some reason...

@youngbupark youngbupark changed the title Reduce test concurrency to 1 Clean up resources even though AWS resources are not used Nov 10, 2022
@youngbupark youngbupark changed the title Clean up resources even though AWS resources are not used [WIP] Clean up resources even though AWS resources are not used Nov 11, 2022
@youngbupark youngbupark changed the title [WIP] Clean up resources even though AWS resources are not used Clean up resources even though AWS resources are not used Nov 11, 2022
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.CoreRPResources == nil && step.SkipKubernetesOutputResourceValidation) || step.SkipResourceDeletion {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we remove the continue here and change the logic in this line so that we do not add similar regressions if some cleanup gets added after this?

Copy link
Author

@youngbupark youngbupark Nov 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah this condition is true only if CoreRPResource is empty and skipped explicitly. So generally, continue will not be executed.

@youngbupark youngbupark merged commit 67321d6 into main Nov 11, 2022
@youngbupark youngbupark deleted the youngp/fix-ftest branch November 11, 2022 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

functional test does not clean up core rp resources
5 participants