[go: up one dir, main page]
Skip to content
Test Nebari Provider

Test Nebari Provider #198

Sign in to view logs

Test Nebari Provider

Test Nebari Provider #198

Triggered via schedule September 29, 2024 03:23
@pullpull[bot]
⁠ 2bac8aa
develop
Status Failure
Total duration 49m 26s
Artifacts –

test-provider.yaml

on: schedule
Matrix: Test Nebari Provider
Fit to window
Zoom out
Zoom in

Annotations

36 errors and 18 warnings
Test Nebari Provider (aws, gitlab-ci)
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID 4C31:33720D:2F064F:57DC4C:66F8D318.
Test Nebari Provider (aws, gitlab-ci)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (aws, github-actions)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (aws, github-actions)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (aws, none)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (aws, none)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (azure, gitlab-ci)
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID E809:30B3CE:1266215:22619CB:66F8D34E.
Test Nebari Provider (azure, gitlab-ci)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (azure, none)
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID FFC1:2EF2FA:1FD6C45:202FC8F:66F8D34F.
Test Nebari Provider (azure, none)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (azure, github-actions)
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID 1511:16C815:81DFA08:F8F0CFA:66F8D355.
Test Nebari Provider (azure, github-actions)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (do, gitlab-ci)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (do, gitlab-ci)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (do, github-actions)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (do, github-actions)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (do, none)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (do, none)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (existing, none)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (existing, none)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (existing, github-actions)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (existing, github-actions)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (existing, gitlab-ci)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (existing, gitlab-ci)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (gcp, github-actions)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (gcp, github-actions)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (gcp, gitlab-ci)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (gcp, gitlab-ci)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (local, github-actions)
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID 7801:1A94D9:97E9D5E:99513F6:66F8D38C.
Test Nebari Provider (local, github-actions)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (gcp, none)
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID 9C41:48206:9596823:96FDE97:66F8D393.
Test Nebari Provider (gcp, none)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (local, gitlab-ci)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (local, gitlab-ci)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (local, none)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/failed-workflow-issue-templates/test-provider.md! Resource not accessible by integration
Test Nebari Provider (local, none)
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"repository\" does not match any associated bound claim values"]}
Test Nebari Provider (aws, gitlab-ci)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (aws, github-actions)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (aws, none)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (azure, gitlab-ci)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (azure, none)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (azure, github-actions)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (do, gitlab-ci)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (do, github-actions)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (do, none)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (existing, none)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (existing, github-actions)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (existing, gitlab-ci)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (gcp, github-actions)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (gcp, gitlab-ci)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (local, github-actions)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (gcp, none)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (local, gitlab-ci)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Nebari Provider (local, none)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, hashicorp/vault-action@v2.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/