This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-496 Add multi-namespaces support to DBClusters #1938
Annotations
11 errors, 2 warnings, and 1 notice
|
Provision monitoring
Process completed with exit code 1.
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L34
1) [api] › backup-storages.spec.ts:17:5 › add/list/get/delete s3 backup storage success ──────────
Error: expect(received).toBeTruthy()
Received: false
32 |
33 | // create
> 34 | expect(response.ok()).toBeTruthy()
| ^
35 | const created = await response.json()
36 |
37 | const name = created.name
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:34:25
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L34
1) [api] › backup-storages.spec.ts:17:5 › add/list/get/delete s3 backup storage success ──────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toBeTruthy()
Received: false
32 |
33 | // create
> 34 | expect(response.ok()).toBeTruthy()
| ^
35 | const created = await response.json()
36 |
37 | const name = created.name
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:34:25
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L34
1) [api] › backup-storages.spec.ts:17:5 › add/list/get/delete s3 backup storage success ──────────
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toBeTruthy()
Received: false
32 |
33 | // create
> 34 | expect(response.ok()).toBeTruthy()
| ^
35 | const created = await response.json()
36 |
37 | const name = created.name
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:34:25
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L107
2) [api] › backup-storages.spec.ts:92:5 › add/list/get/delete azure backup storage success ───────
Error: expect(received).toBeTruthy()
Received: false
105 |
106 | // create
> 107 | expect(response.ok()).toBeTruthy()
| ^
108 | const created = await response.json()
109 |
110 | const name = created.name
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:107:25
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L107
2) [api] › backup-storages.spec.ts:92:5 › add/list/get/delete azure backup storage success ───────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toBeTruthy()
Received: false
105 |
106 | // create
> 107 | expect(response.ok()).toBeTruthy()
| ^
108 | const created = await response.json()
109 |
110 | const name = created.name
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:107:25
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L107
2) [api] › backup-storages.spec.ts:92:5 › add/list/get/delete azure backup storage success ───────
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toBeTruthy()
Received: false
105 |
106 | // create
> 107 | expect(response.ok()).toBeTruthy()
| ^
108 | const created = await response.json()
109 |
110 | const name = created.name
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:107:25
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L229
3) [api] › backup-storages.spec.ts:161:5 › create backup storage failures ────────────────────────
Error: expect(received).toMatch(expected)
Expected substring: "'name' is not RFC 1035 compatible"
Received string: "request body has an error: doesn't match schema #/components/schemas/CreateBackupStorageParams: Error at \"/targetNamespaces\": property \"targetNamespaces\" is missing"
227 |
228 | expect(response.status()).toBe(400)
> 229 | expect((await response.json()).message).toMatch(testCase.errorText)
| ^
230 | }
231 | })
232 |
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:229:45
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L229
3) [api] › backup-storages.spec.ts:161:5 › create backup storage failures ────────────────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toMatch(expected)
Expected substring: "'name' is not RFC 1035 compatible"
Received string: "request body has an error: doesn't match schema #/components/schemas/CreateBackupStorageParams: Error at \"/targetNamespaces\": property \"targetNamespaces\" is missing"
227 |
228 | expect(response.status()).toBe(400)
> 229 | expect((await response.json()).message).toMatch(testCase.errorText)
| ^
230 | }
231 | })
232 |
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:229:45
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L229
3) [api] › backup-storages.spec.ts:161:5 › create backup storage failures ────────────────────────
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toMatch(expected)
Expected substring: "'name' is not RFC 1035 compatible"
Received string: "request body has an error: doesn't match schema #/components/schemas/CreateBackupStorageParams: Error at \"/targetNamespaces\": property \"targetNamespaces\" is missing"
227 |
228 | expect(response.status()).toBe(400)
> 229 | expect((await response.json()).message).toMatch(testCase.errorText)
| ^
230 | }
231 | })
232 |
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:229:45
|
|
Run integration tests:
api-tests/tests/backup-storages.spec.ts#L246
4) [api] › backup-storages.spec.ts:233:5 › update backup storage failures ────────────────────────
Error: expect(received).toBeTruthy()
Received: false
244 | })
245 |
> 246 | expect(response.ok()).toBeTruthy()
| ^
247 | const created = await response.json()
248 |
249 | const name = created.name
at /home/runner/work/percona-everest-backend/percona-everest-backend/api-tests/tests/backup-storages.spec.ts:246:25
|
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: percona-platform/setup-go@v4, percona-platform/cache@v3, medyagh/setup-minikube@latest. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Set up Go release
Restore cache failed: Dependencies file is not found in /home/runner/work/percona-everest-backend/percona-everest-backend. Supported file pattern: go.sum
|
|
Run integration tests
42 failed
[api] › backup-storages.spec.ts:17:5 › add/list/get/delete s3 backup storage success ───────────
[api] › backup-storages.spec.ts:92:5 › add/list/get/delete azure backup storage success ────────
[api] › backup-storages.spec.ts:161:5 › create backup storage failures ─────────────────────────
[api] › backup-storages.spec.ts:233:5 › update backup storage failures ─────────────────────────
[api] › database-cluster-backups.spec.ts:18:5 › create/delete database cluster backups ─────────
[api] › database-cluster-backups.spec.ts:55:5 › dbcluster not found ────────────────────────────
[api] › database-cluster-backups.spec.ts:83:5 › list backups ───────────────────────────────────
[api] › database-cluster-restores.spec.ts:19:5 › create/update/delete database cluster restore ─
[api] › database-cluster-restores.spec.ts:85:5 › list restores ─────────────────────────────────
[api] › database-cluster-restores.spec.ts:176:5 › create restore: validation errors ────────────
[api] › database-cluster.spec.ts:55:5 › create db cluster with monitoring config ───────────────
[api] › database-cluster.spec.ts:109:5 › update db cluster with a new monitoring config ────────
[api] › database-cluster.spec.ts:177:5 › update db cluster without monitoring config with a new monitoring config
[api] › database-cluster.spec.ts:242:5 › update db cluster monitoring config with an empty monitoring config
[api] › database-engines.spec.ts:17:5 › check operators are installed ──────────────────────────
[api] › database-engines.spec.ts:35:5 › get/edit database engine versions ──────────────────────
[api] › kubernetes.spec.ts:33:5 › enable/disable cluster-monitoring ────────────────────────────
[api] › monitoring-instances.spec.ts:36:5 › create monitoring instance with api key ────────────
[api] › monitoring-instances.spec.ts:56:5 › create monitoring instance with user/password ──────
[api] › monitoring-instances.spec.ts:77:5 › create monitoring instance missing pmm ─────────────
[api] › monitoring-instances.spec.ts:89:5 › create monitoring instance missing pmm credentials ─
[api] › monitoring-instances.spec.ts:102:5 › list monitoring instances ─────────────────────────
[api] › monitoring-instances.spec.ts:115:5 › get monitoring instance ───────────────────────────
[api] › monitoring-instances.spec.ts:128:5 › delete monitoring instance ────────────────────────
[api] › monitoring-instances.spec.ts:150:5 › patch monitoring instance ─────────────────────────
[api] › monitoring-instances.spec.ts:169:5 › patch monitoring instance secret key changes ──────
[api] › monitoring-instances.spec.ts:192:5 › patch monitoring instance type updates properly ───
[api] › monitoring-instances.spec.ts:212:5 › patch monitoring instance type fails on missing key
[api] › monitoring-instances.spec.ts:232:5 › create monitoring instance failures ───────────────
[api] › monitoring-instances.spec.ts:237:5 › update monitoring instances failures ──────────────
[api] › monitoring-instances.spec.ts:272:5 › update: monitoring instance not found ─────────────
[api] › monitoring-instances.spec.ts:279:5 › delete: monitoring instance not found ─────────────
[api] › monitoring-instances.spec.ts:286:5 › get: monitoring instance not found ────────────────
[api] › pg-clusters.spec.ts:32:5 › create/edit/delete single node pg cluster ───────────────────
[api] › pg-clusters.spec.ts:114:5 › expose pg cluster after creation ───────────────────────────
[api] › pg-clusters.spec.ts:192:5 › expose pg cluster on EKS to the public internet and scale up
[api] › psmdb-clusters.spec.ts:23:5 › create/edit/delete single node psmdb cluster ─────────────
[api] › psmdb-clusters.spec.ts:105:5 › expose psmdb cluster after creation ─────────────────────
[api] › psmdb-clusters.spec.ts:189:5 › expose psmdb cluster on EKS to the public internet and scale up
[api] › pxc-clusters.spec.ts:36:5 › create/edit/delete pxc single node cluster ─────────────────
|
The logs for this run have expired and are no longer available.
Loading