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

Scheduled functional test failed - Run ID: 5608724856 #6308

Closed
rad-ci-bot opened this issue Jul 20, 2023 · 3 comments
Closed

Scheduled functional test failed - Run ID: 5608724856 #6308

rad-ci-bot opened this issue Jul 20, 2023 · 3 comments
Assignees

Comments

@rad-ci-bot
Copy link
Collaborator

rad-ci-bot commented Jul 20, 2023

Bug information

This bug is generated automatically if the scheduled functional test fails. The Radius functional test operates on a schedule of every 4 hours during weekdays and every 12 hours over the weekend. It's important to understand that the test may fail due to workflow infrastructure issues, like network problems, rather than the flakiness of the test itself. For the further investigation, please visit here.

AB#8769

AB#9513

@lakshmimsft
Copy link
Contributor

lakshmimsft commented Jul 24, 2023

Findings so far:
Login into Azure occurs at 08:32:39:
image

Error occurs at 08:36:44 (4min 5 sec):
image
There seems to be a glitch is retrieving the refreshed token.

One possible way going ahead is to increase AZURE_CLI_LOGIN_TIMEOUT env variable to larger value Before calling az login in the workflow file. Think the only way to know more is to create PRs and read existing (default)values and confirm we can update the timeouts to say (45 min) and confirm workflow passes.
Will follow up with adding tasks in ADO for this issue and creating a PR..

@lakshmimsft lakshmimsft self-assigned this Jul 24, 2023
@AaronCrawfis
Copy link
Contributor

Is AZURE_CLI_LOGIN_TIMEOUT documented in the Azure CLI docs as a valid flag?

@willtsai willtsai transferred this issue from radius-project/radius Sep 19, 2023
@AaronCrawfis AaronCrawfis transferred this issue from another repository Sep 19, 2023
@willdavsmith
Copy link
Contributor

Closing, test logs have expired.

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

No branches or pull requests

4 participants