Skip to content

fix(deps): update module github.com/restic/restic to v0.17.3 #2695

fix(deps): update module github.com/restic/restic to v0.17.3

fix(deps): update module github.com/restic/restic to v0.17.3 #2695

GitHub Actions / e2e-report failed Nov 8, 2024 in 0s

10 tests run, 9 passed, 0 skipped, 1 failed.

Annotations

Check failure on line 1 in e2e/node_modules/bats/man/bats.1

See this annotation in the file changed.

@github-actions github-actions / e2e-report

bats.Given an existing Restic repository, When creating a Restore, Then Restore to PVC

(from function `expect_file_in_container' in file ./lib/k8up.bash, line 480,
 in test file ./test-04-restore.bats, line 39)
Raw output
(from function `expect_file_in_container' in file ./lib/k8up.bash, line 480,
 in test file ./test-04-restore.bats, line 39)
  `expect_file_in_container 'deploy/subject-deployment' 'subject-container' "/data/${expected_filename}" "${expected_content}"' failed
release "k8up" uninstalled
Release "k8up" does not exist. Installing it now.
NAME: k8up
LAST DEPLOYED: Fri Nov  8 22:38:35 2024
NAMESPACE: k8up-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
#####################
! Attention !
#####################

This Helm chart does not include CRDs.
Please make sure you have installed or upgraded the necessary CRDs as instructed in the Chart README.

#####################
  A running operator is ready
namespace "k8up-e2e-subject" deleted
removed directory './debug/data/pvc-subject'
namespace/k8up-e2e-subject created
  The namespace 'k8up-e2e-subject' is ready.
persistentvolumeclaim/subject-pvc created
deployment.apps/subject-deployment created
  The subject is ready
secret/backup-credentials created
secret/backup-repo created
backup.k8up.io/k8up-backup created
Waiting for 'backup/k8up-backup' in namespace 'k8up-e2e-subject' to become 'completed' ...
backup.k8up.io/k8up-backup condition met
Valid expression. Verification in progress...
k8up-backup has the right value (succeeded).
  An existing backup is ready
namespace "k8up-e2e-subject" deleted
removed directory './debug/data/pvc-subject'
namespace/k8up-e2e-subject created
  The namespace 'k8up-e2e-subject' is ready.
persistentvolumeclaim/subject-pvc created
deployment.apps/subject-deployment created
  The subject is ready
secret/backup-credentials created
secret/backup-repo created
restore.k8up.io/k8up-restore created
Valid expression. Verification in progress...
k8up-restore has the right value (true).
Valid expression. Verification in progress...
restore-k8up-restore has the right value (1).
Waiting for 'restore/k8up-restore' in namespace 'k8up-e2e-subject' to become 'completed' ...
restore.k8up.io/k8up-restore condition met
Valid expression. Verification in progress...
k8up-restore has the right value (succeeded).
Testing if file '/data/old_file.txt' contains 'Old content: 1731105511' in container 'subject-container' of pod 'deploy/subject-deployment':
> by running the command `sh -c 'ls -la "/data"'`.
total 8
drwxrwxrwx    2 root     root            60 Nov  8 22:40 .
drwxr-xr-x    1 root     root          4096 Nov  8 22:40 ..
-rw-r--r--    1 1001     root            23 Nov  8 22:40 new_file.txt
↩
> by running the command `sh -c 'test -f "/data/old_file.txt"'`.
command terminated with exit code 1