GUI acceptance tests using environment deployed from packages.

Build: #2144 was successful

Job: Onepanel two hosts deployment was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
5 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
1
Successful since
#2082 ()

Tests

  • 1 test in total
  • 4 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  34723      0 --:--:-- --:--:-- --:--:-- 34723
Error response from daemon: Cannot kill container: 5f37691e16f8: Container 5f37691e16f8c5de35b91f128f2910bde6611e0e379f02c25c73b1992ae45709 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-CO2HDT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CO2HDT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CO2HDT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CO2HDT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CO2HDT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CO2HDT/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-CO2HDT/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-CO2HDT/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-CO2HDT/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
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]
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]
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
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  47479      0 --:--:-- --:--:-- --:--:-- 47479
Error from server (NotFound): pods "dev-oneprovider-krakow-1" not found
Error response from daemon: Cannot kill container: 30af713fc475: Container 30af713fc475270db100d5a7f6e71051d649a338eebb207d76173d7ea909a4e4 is not running
Error response from daemon: Cannot kill container: 43357902e362: Container 43357902e3621f1f9fcfac404e98a4b04b538aed8e451f0034771c048bbb3403 is not running
Error response from daemon: Cannot kill container: f7263579124f: Container f7263579124f25a21fdd72764ef330c357db0303617046e7f6064d838a583110 is not running
Error response from daemon: Cannot kill container: b40abed236d5: Container b40abed236d536e3147556ede31c4611dd8a2a4928384aa743d56ea440fd95d4 is not running
Error response from daemon: Cannot kill container: 31b5721a000e: Container 31b5721a000ef2a860e863c946950ee58142a22dcc724e73ea92ac3332c5a08e is not running
Error response from daemon: Cannot kill container: adc946ce16c9: Container adc946ce16c99fde38f7854cbfcff396a6907528a5baf629188b94f47018d795 is not running
Error response from daemon: Cannot kill container: 0f1002a82de2: Container 0f1002a82de266df9db51839a0847e6421b3755230332f0a8998c2e34ff7110f is not running
Error response from daemon: Cannot kill container: 311207d1571c: Container 311207d1571cdb178b0489786b904dd041b3105d59e506b65ad41b11cb1cda1e is not running
Error response from daemon: Cannot kill container: 7caf9b5a3d4b: Container 7caf9b5a3d4bbc0e5abde2a2d7ea43fd248237c7f106728f66b7d2425f33c763 is not running
Error response from daemon: Cannot kill container: b966eefa76d7: Container b966eefa76d742ea7fc4fd20275ea5d427e2d29197f13e89f53496c3a42850e4 is not running