Flaky test: Failed to restore AWS bicep artifact

[rad-ci-bot]

Bug information

This issue is automatically generated if the scheduled long running test fails. The Radius long running test operates on a schedule of every 2 hours everyday. 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#13960

[radius-triage-bot]

👋 @rad-ci-bot 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

[radius-triage-bot]

👍 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]

The latest tag is on ACR so this might be a race case where the artifact doesn't get restored before the build step starts. Doesn't seem to be an issue with ACR uploads or downloads as the latest tag is present.

cli.go:341: [rad] /home/runner/work/radius/radius/test/functional-portable/corerp/cloud/resources/testdata/aws-s3-bucket.bicep(1,11) : Error BCP190: The artifact with reference "br:biceptypes.azurecr.io/aws:latest" has not been restored. [https://aka.ms/bicep/core-diagnostics#BCP190]
    cli.go:341: [rad] /home/runner/work/radius/radius/test/functional-portable/corerp/cloud/resources/testdata/aws-s3-bucket.bicep(6,17) : Error BCP029: The resource type is not valid. Specify a valid resource type of format "<type-name>@<apiVersion>". [https://aka.ms/bicep/core-diagnostics#BCP029]
    cli.go:341: [rad] Error: failed executing "/home/runner/.rad/bin/rad-bicep build --stdout /home/runner/work/radius/radius/test/functional-portable/corerp/cloud/resources/testdata/aws-s3-bucket.bicep": exit status 1
    cli.go:341: [rad] 
    cli.go:341: [rad] TraceId:  71ce6f58f8fe101f7f9a5cb1e5dda569
    cli.go:341: [rad] 
    cli.go:341: [rad] 
    deployexecutor.go:83: 
        	Error Trace:	/home/runner/work/radius/radius/test/step/deployexecutor.go:83
        	            				/home/runner/work/radius/radius/test/rp/rptest.go:392
        	Error:      	Received unexpected error:
        	            	command 'rad deploy /home/runner/work/radius/radius/test/functional-portable/corerp/cloud/resources/testdata/aws-s3-bucket.bicep --parameters bucketName=radiusfunctionaltestbucket-dfda1722-eeed-42df-89f0-b36d5[98](https://github.com/radius-project/radius/actions/runs/12597393259/job/35110307335#step:21:99)8a233 --parameters creationTimestamp=1735906225' had non-zero exit code: exit status 1
        	Test:       	Test_AWS_S3Bucket/deploy_testdata/aws-s3-bucket.bicep
        	Messages:   	failed to deploy deploy testdata/aws-s3-bucket.bicep

[kachawla]

This is happening frequently, 3 occurrences in the last 2 days (and 5 in the last week based on references above):

#8225
#8229
#8235

Removing the triage and oncall label as the depth and investigation required is beyond the scope of oncall. Also going to add important label to bring it to top of the queue for the planning discussion this week.

[radius-triage-bot]

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