radius-project / radius

Radius is a cloud-native, portable application platform that makes app development easier for teams building cloud-native apps.
https://radapp.io
Apache License 2.0
1.48k stars 94 forks source link

Scheduled functional test failure - Test_PersistentVolume #7168

Open sk593 opened 8 months ago

sk593 commented 8 months ago

Steps to reproduce

This was a failure during a scheduled functional test run

Observed behavior

=== FAIL: test/functional/shared/resources Test_PersistentVolume/deploy_testdata/corerp-resources-volume-azure-keyvault.bicep (17.12s)
    rptest.go:272: running step 0 of 1: deploy testdata/corerp-resources-volume-azure-keyvault.bicep
    deployexecutor.go:80: deploying deploy testdata/corerp-resources-volume-azure-keyvault.bicep from file testdata/corerp-resources-volume-azure-keyvault.bicep
    cli.go:4[71](https://github.com/radius-project/radius/actions/runs/7808217262/job/21298182968#step:26:72): [heartbeat] command rad deploy /home/runner/work/radius/radius/test/functional/shared/resources/testdata/corerp-resources-volume-azure-keyvault.bicep --parameters magpieimage=ghcr.io/radius-project/dev/magpiego:pr-28e4117d48 --parameters oidcIssuer=https://radiusoidc.blob.core.windows.net/kubeoidc/ is still running after 10.000566026s
make: *** [build/test.mk:70: test-functional-shared] Error 1
    cli.go:418: [rad] Building /home/runner/work/radius/radius/test/functional/shared/resources/testdata/corerp-resources-volume-azure-keyvault.bicep...
    cli.go:418: [rad] Error: unexpected end of JSON input
    cli.go:418: [rad] 
    cli.go:418: [rad] TraceId:  6098521666a7d6ebd178bff5687db344
    cli.go:418: [rad] 
    cli.go:418: [rad] 
    deployexecutor.go:83: 
            Error Trace:    /home/runner/work/radius/radius/test/step/deployexecutor.go:83
                                        /home/runner/work/radius/radius/test/functional/shared/rptest.go:2[73](https://github.com/radius-project/radius/actions/runs/7808217262/job/21298182968#step:26:74)
            Error:          Received unexpected error:
                            command 'rad deploy /home/runner/work/radius/radius/test/functional/shared/resources/testdata/corerp-resources-volume-azure-keyvault.bicep --parameters magpieimage=ghcr.io/radius-project/dev/magpiego:pr-28e4117d48 --parameters oidcIssuer=https://radiusoidc.blob.core.windows.net/kubeoidc/' had non-zero exit code: exit status 1
            Test:           Test_PersistentVolume/deploy_testdata/corerp-resources-volume-azure-keyvault.bicep
            Messages:       failed to deploy deploy testdata/corerp-resources-volume-azure-keyvault.bicep
    --- FAIL: Test_PersistentVolume/deploy_testdata/corerp-resources-volume-azure-keyvault.bicep (17.12s)

Desired behavior

This test should consistently pass without failures

Workaround

No response

rad Version

PR version

Operating system

No response

Additional context

No response

Would you like to support us?

AB#11157

radius-triage-bot[bot] commented 8 months ago

:wave: @sk593 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

sk593 commented 8 months ago

Since the error is related to malformed json, I think it may have either been a deployment engine issue once the bicep template gets processed or an issue with the OIDC JWT. Given that the env/app deployments started, it seems more likely to be an OIDC issue. There were 500 failures in the workload identity pod logs but not information on what caused it so that may be related. It’s possible that we need more logging in the federated identity code if there’s issues.

radius-triage-bot[bot] commented 7 months ago

:+1: 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