Skip to content

fix rbac miss role bug #1277

fix rbac miss role bug

fix rbac miss role bug #1277

Triggered via pull request November 7, 2024 10:28
Status Failure
Total duration 6m 18s
Artifacts 1

main.yaml

on: pull_request
Matrix: test-backup-restore-cli
Matrix: test-backup-restore-after-upgrade
Matrix: test-backup-restore-cross-version
Matrix: test-backup-restore-with-custom-config
Matrix: test-backup-restore-api
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 20 warnings
test-backup-restore-cli (docker-compose, standalone, standalone)
Process completed with exit code 1.
test-backup-restore-cli (docker-compose, standalone, cluster)
Process completed with exit code 1.
test-backup-restore-cli (docker-compose, cluster, standalone)
Process completed with exit code 1.
test-backup-restore-cli (docker-compose, cluster, cluster)
Process completed with exit code 1.
test-backup-restore-with-custom-config (helm, standalone, milvus-bucket)
Process completed with exit code 1.
test-backup-restore-with-custom-config (helm, standalone, milvus-bucket)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
test-backup-restore-with-custom-config (helm, standalone, file, milvus-bucket)
Process completed with exit code 1.
test-backup-restore-with-custom-config (helm, standalone, milvus-backup)
Process completed with exit code 1.
test-backup-restore-with-custom-config (helm, standalone, milvus-backup)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
test-backup-restore-with-custom-config (helm, standalone, file, milvus-backup)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
test-backup-restore-with-custom-config (helm, standalone, file, milvus-backup)
Process completed with exit code 1.
test-backup-restore-cli (docker-compose, standalone, standalone)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-cli (docker-compose, standalone, cluster)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-cli (docker-compose, cluster, standalone)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-cli (docker-compose, cluster, cluster)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-after-upgrade (docker-compose, standalone, standalone, v2.3.12, master-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-after-upgrade (docker-compose, standalone, standalone, 2.3-latest, master-lat...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-after-upgrade (docker-compose, standalone, standalone, 2.3-latest, 2.3-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-cross-version (docker-compose, standalone, standalone, 2.3-latest, master-lat...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-after-upgrade (docker-compose, standalone, standalone, v2.3.12, 2.3-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-cross-version (docker-compose, standalone, standalone, 2.2.0-latest, master-l...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-cross-version (docker-compose, standalone, standalone, 2.3-latest, 2.4-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-cross-version (docker-compose, standalone, standalone, 2.2.0-latest, 2.4-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-with-custom-config (helm, standalone, milvus-bucket)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, helm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-with-custom-config (helm, standalone, file, milvus-bucket)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, helm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-with-custom-config (helm, standalone, milvus-backup)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, helm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-backup-restore-with-custom-config (helm, standalone, file, milvus-backup)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, helm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
custom-config-helm-standalone
53.2 KB