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

AADSTS700024: Client assertion is not within its valid time range error in Purge Test Resources workflow #7550

Closed
1 task
ytimocin opened this issue Apr 26, 2024 · 3 comments · Fixed by #7551
Assignees
Labels
bug Something is broken or not working as expected important This item is a high priority Issue we intend to address as soon as possible triaged This issue has been reviewed and triaged

Comments

@ytimocin
Copy link
Contributor

ytimocin commented Apr 26, 2024

Steps to reproduce

Today I noticed that our functional tests were failing due to number of resource groups we have: https://teams.microsoft.com/l/message/19:ve3Qj3hke37Z4b1EdjJy-K4nzh3nDgRxZJJARwusRgc1@thread.tacv2/1714089575308?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=b33db407-e89b-4fb6-87cc-9b2f9f8ec265&parentMessageId=1714089575308&teamName=Radius%20Core%20Team&channelName=General&createdTime=1714089575308.

I, then, checked the Purge Test Resources workflow to see that it had been failing for a while: https://github.com/radius-project/radius/actions/workflows/purge-test-resources.yaml.

Observed behavior

Test resources were not being purged for a while.

Desired behavior

  1. Test resources being purged
  2. Issue gets created if there is a problem with the Purge test resources workflow

Workaround

Manually deleting the resource groups.

rad Version

0.32

Operating system

No response

Additional context

No response

Would you like to support us?

  • Yes, I would like to support you

AB#12161

@ytimocin ytimocin added the bug Something is broken or not working as expected label Apr 26, 2024
@radius-triage-bot
Copy link

👋 @ytimocin Thanks for filing this bug report.

A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.

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

@ytimocin ytimocin self-assigned this Apr 26, 2024
@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 Apr 29, 2024
@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

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken or not working as expected important This item is a high priority Issue we intend to address as soon as possible triaged This issue has been reviewed and triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants