GUI acceptance tests using environment deployed from packages.

Build: #2152 was successful

Job: Onezone tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
1455adf71c99919c72b4566dc449001255aebcdf
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 12 minutes taken in total.

Error summary

The build generated some errors. See the full build log for more details.

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  39432      0 --:--:-- --:--:-- --:--:-- 39432
Error response from daemon: Cannot kill container: 6726e6fd8dd7: Container 6726e6fd8dd78f3a935a04b90eabe33b34214c70e2a9737a8658007ce2dbfa8c is not running
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'bamboos'
Submodule 'cdmi_swagger' (ssh://git@git.onedata.org:7999/vfs/cdmi-swagger.git) registered for path 'cdmi_swagger'
Submodule 'one_env' (ssh://git@git.onedata.org:7999/vfs/one-env.git) registered for path 'one_env'
Submodule 'onepanel_swagger' (ssh://git@git.onedata.org:7999/vfs/onepanel-swagger.git) registered for path 'onepanel_swagger'
Submodule 'oneprovider_swagger' (ssh://git@git.onedata.org:7999/vfs/oneprovider-swagger.git) registered for path 'oneprovider_swagger'
Submodule 'onezone_swagger' (ssh://git@git.onedata.org:7999/vfs/onezone-swagger.git) registered for path 'onezone_swagger'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onezone_swagger'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onepanel_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onepanel_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'oneprovider_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/oneprovider_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onezone_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
W0527 11:39:30.605841     489 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  45174      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 532eaa6e7e17: Container 532eaa6e7e17856a1cbd7d2dff6d8659bfd350460a47fbf542e2dbec66cf793a is not running
Error response from daemon: Cannot kill container: dc9821c70016: Container dc9821c700167e300c633438bde0d9f6104bd5e95473c7694e1e05b91259b1c0 is not running
Error response from daemon: Cannot kill container: af163919c77f: Container af163919c77f40c831509ded6a2b6fb69af13d6e4c2376758d0aa90d8109484b is not running
Error response from daemon: Cannot kill container: 5791d2b7417d: Container 5791d2b7417d9a121627191183ab92e75e1558daef27645fe1136d632a12fdec is not running
Error response from daemon: Cannot kill container: 3922dbeb8ff2: Container 3922dbeb8ff2d72f45d8709c7ca79d982c22e5e79a3c3f857771608b5f15f0a4 is not running
Error response from daemon: Cannot kill container: 57dadc2896a4: Container 57dadc2896a4b9618e104fc364c3541a9cd2785e48e5653f88583a855c24c705 is not running
Error response from daemon: Cannot kill container: 7e1dc9a6ac57: Container 7e1dc9a6ac578bbb02b9235f4bc9b1b744b939714cc4b5766e63b506f54d3659 is not running
Error response from daemon: Cannot kill container: 5d60056b52ed: Container 5d60056b52edd022f3fd01302c2c807c4c7026ddbeb32e57f5326473cd8ab5de is not running
Error response from daemon: Cannot kill container: b4bd26e1e354: Container b4bd26e1e354812dc91596f4463013d26538f5d7a199f7314d7a776badaf72e2 is not running
Error response from daemon: Cannot kill container: abf2281d7472: Container abf2281d74729d2de463f2eed8dcba4e7470e518072f64c0fb9c5bf1da5153d4 is not running
Error response from daemon: Cannot kill container: e7394811000d: Container e7394811000d55717f5a4e7fafc21b057886f889adaa558d6e33a63ac798a949 is not running
Error response from daemon: Cannot kill container: 1c2ca585beaf: Container 1c2ca585beafdb95e0662f4303e173ef1bf5c469ec94f3b1be6c438d289555c9 is not running
Error response from daemon: Cannot kill container: 93d237e0c9b2: Container 93d237e0c9b20bdc8315975fd9a38b8c219e8244ca7f75a4b6a5ea0420c19d8d is not running
Error response from daemon: Cannot kill container: 4c89dfbc6ceb: Container 4c89dfbc6ceb86a6842124fa86273147be1da7a3c27924dccabf5375c8137e2a is not running
Error response from daemon: Cannot kill container: f43bff95f8f8: Container f43bff95f8f8d584363994f68648547425095176057c0cd5c2e9d1c4dccdd040 is not running
Error response from daemon: Cannot kill container: c76e6ae32073: Container c76e6ae320730f8708d0e1804c1c5036006f785ac3d55c3c96a50ea197c6395d is not running
Error response from daemon: Cannot kill container: a7f5ab75a562: Container a7f5ab75a562113718f1335d5e639285f849e0d51ee88606029de011ee11c775 is not running
Error response from daemon: Cannot kill container: 7dba9a281378: Container 7dba9a28137854da944c7f322a0133a1ef5539f8becc4c485989f26158286732 is not running
Error response from daemon: Cannot kill container: a355ac9f66ca: Container a355ac9f66ca60b62b4d569291ad93873610725ad205aa6ec5c362dee2c74a5a is not running
Error response from daemon: Cannot kill container: 2748f9df65e5: Container 2748f9df65e5e4e182a26d76e4453b519615cea210da45bc43ea731f96df4693 is not running