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.

Sign up for GitHub

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

Jump to bottom

Add resiliency to the GET operation of AWS resource deployments #7352

Open
1 task done
willdavsmith opened this issue Mar 19, 2024 · 3 comments · May be fixed by #8170
Open
1 task done

Add resiliency to the GET operation of AWS resource deployments #7352

willdavsmith opened this issue Mar 19, 2024 · 3 comments · May be fixed by #8170
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged

Comments

@willdavsmith
Copy link
Contributor

willdavsmith commented Mar 19, 2024 •
edited by azure-boards bot
Loading

Overview of feature request

Sometimes in the functional tests (and potentially for users), we see a failed AWS deployment due to a GET call returning 404. We should investigate why the call fails and potentially add retries to resolve this.

Example: https://github.com/radius-project/radius/actions/runs/8311733036/job/22745893415
It looks like the deployment fails because it cannot find the bucket after it is created. Checking the console will show that the bucket is created. (it's left hanging)

My hypothesis is that AWS takes a minute to register the bucket as created sometimes.

Acceptance criteria

  • Retries for the GET call have been added

Additional context

Related issue: #5963

Would you like to support us?

  • Yes, I would like to support you

AB#11554
@willdavsmith willdavsmith added the feature This issue describes a feature request in Radius label Mar 19, 2024
@radius-triage-bot
Copy link

👋 @willdavsmith Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@sylvainsf sylvainsf added triaged This issue has been reviewed and triaged important This item is a high priority Issue we intend to address as soon as possible labels Mar 21, 2024
@radius-triage-bot
Copy link

We've prioritized work on this issue. Please subscribe to this issue for notifications, we'll provide updates as we make progress.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@radius-triage-bot
Copy link

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@sk593 sk593 mentioned this issue Apr 9, 2024
Closed
@sylvainsf sylvainsf removed the important This item is a high priority Issue we intend to address as soon as possible label May 6, 2024
@willdavsmith willdavsmith linked a pull request Dec 30, 2024 that will close this issue
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add retry logic to UCP GetAWSResourceWithPost handler willdavsmith/radius
2 participants
@sylvainsf @willdavsmith