GUI acceptance tests using environment deployed from packages.

Build: #646 failed

Job: Chrome metadata test failed

Job result summary

Completed
Duration
29 minutes
Revision
1250895e54287fb5b835eb62f6db05eaf6d1f7f1
Total tests
27
Fixed in
#650 (Child of ODSRV-OZP-1255)

Configuration changes

Job Chrome metadata test with key ODSRV-GAPT-MTC no longer exists.

Tests

  • 27 tests in total
  • 27 tests failed
  • 27 failures are new
  • 20 minutes taken in total.
New test failures 27
Status Test Duration
Collapse Failed test_metadata test_add_metadata_to_directory_clicks_both_add_icon_and_save_all_changes_button[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_metadata_to_directory_clicks_both_add_icon_and_save_all_changes_button[1oz_1op_deployed]'>>

    from tests.gui.steps.oneprovider_common import *
>   from tests.gui.meta_steps.onezone.common import *

tests/gui/scenarios/test_metadata.py:49: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(78 more lines...)
Collapse Failed test_metadata test_add_metadata_to_directory_clicks_only_save_all_changes_button[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_metadata_to_directory_clicks_only_save_all_changes_button[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:53: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_add_metadata_to_file_clicks_both_add_icon_and_save_all_changes_button[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_metadata_to_file_clicks_both_add_icon_and_save_all_changes_button[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:53: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_add_metadata_to_file_clicks_only_save_all_changes_button[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_metadata_to_file_clicks_only_save_all_changes_button[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:57: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_add_valid_metadata_to_directory_in_json_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_valid_metadata_to_directory_in_json_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:69: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_add_valid_metadata_to_directory_in_rdf_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_valid_metadata_to_directory_in_rdf_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:81: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_add_valid_metadata_to_file_in_json_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_valid_metadata_to_file_in_json_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:73: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_add_valid_metadata_to_file_in_xml_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_add_valid_metadata_to_file_in_xml_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:85: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_delete_directory_metadata_in_json_format[1oz_1op_deployed]
39 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_delete_directory_metadata_in_json_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:73: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_delete_directory_metadata_in_xml_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_delete_directory_metadata_in_xml_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:85: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_delete_file_metadata_in_json_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_delete_file_metadata_in_json_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:77: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_delete_file_metadata_in_xml_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_delete_file_metadata_in_xml_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:89: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_delete_single_basic_metadata_entry_for_directory[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_delete_single_basic_metadata_entry_for_directory[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:57: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_delete_single_basic_metadata_entry_for_file[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_delete_single_basic_metadata_entry_for_file[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:61: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_discard_changes_while_entering_metadata_for_directory_in_json_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_discard_changes_while_entering_metadata_for_directory_in_json_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:77: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_discard_changes_while_entering_metadata_for_directory_in_xml_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_discard_changes_while_entering_metadata_for_directory_in_xml_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:89: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_discard_changes_while_entering_metadata_for_file_in_json_format[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_discard_changes_while_entering_metadata_for_file_in_json_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:81: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_discard_changes_while_entering_metadata_for_file_in_xml_format[1oz_1op_deployed]
51 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_discard_changes_while_entering_metadata_for_file_in_xml_format[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:93: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_edit_metadata_icon_is_visible_if_directory_has_basic_metadata_entry[1oz_1op_deployed]
3 mins
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_edit_metadata_icon_is_visible_if_directory_has_basic_metadata_entry[1oz_1op_deployed]'>>

    from tests.gui.steps.oneprovider.data_tab import *
>   from tests.gui.steps.oneprovider.file_browser import *

tests/gui/scenarios/test_metadata.py:41: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(78 more lines...)
Collapse Failed test_metadata test_edit_metadata_icon_is_visible_if_file_has_basic_metadata_entry[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_edit_metadata_icon_is_visible_if_file_has_basic_metadata_entry[1oz_1op_deployed]'>>

    from tests.gui.steps.oneprovider.groups import *
>   from tests.gui.steps.oneprovider.spaces import *

tests/gui/scenarios/test_metadata.py:45: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(78 more lines...)
Collapse Failed test_metadata test_invalid_basic_metadata_entry_for_directory_should_be_colored_red[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_invalid_basic_metadata_entry_for_directory_should_be_colored_red[1oz_1op_deployed]'>>

    from tests.gui.steps.oneprovider.groups import *
>   from tests.gui.steps.oneprovider.spaces import *

tests/gui/scenarios/test_metadata.py:45: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(78 more lines...)
Collapse Failed test_metadata test_invalid_basic_metadata_entry_for_file_should_be_colored_red[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_invalid_basic_metadata_entry_for_file_should_be_colored_red[1oz_1op_deployed]'>>

    from tests.gui.steps.oneprovider_common import *
>   from tests.gui.meta_steps.onezone.common import *

tests/gui/scenarios/test_metadata.py:49: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(78 more lines...)
Collapse Failed test_metadata test_open_metadata_panel_and_check_presence_of_navigation_tabs[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_open_metadata_panel_and_check_presence_of_navigation_tabs[1oz_1op_deployed]'>>

    from tests.gui.steps.oneprovider.data_tab import *
>   from tests.gui.steps.oneprovider.file_browser import *

tests/gui/scenarios/test_metadata.py:41: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(78 more lines...)
Collapse Failed test_metadata test_user_should_not_see_any_metadata_for_directory_after_clicking_remove_metadata_button[1oz_1op_deployed]
39 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_should_not_see_any_metadata_for_directory_after_clicking_remove_metadata_button[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:61: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_user_should_not_see_any_metadata_for_file_after_clicking_remove_metadata_button[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_should_not_see_any_metadata_for_file_after_clicking_remove_metadata_button[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:65: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_user_starts_adding_metadata_to_directory_but_discards_changes[1oz_1op_deployed]
38 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_starts_adding_metadata_to_directory_but_discards_changes[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:65: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)
Collapse Failed test_metadata test_user_starts_adding_metadata_to_file_but_discards_changes[1oz_1op_deployed]
37 secs
RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_starts_adding_metadata_to_file_but_discards_changes[1oz_1op_deployed]'>>

>   ???

tests/gui/scenarios/test_metadata.py:69: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)

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  3921  100  3921    0     0   7405      0 --:--:-- --:--:-- --:--:--  7412
Error response from daemon: Cannot kill container 986a4d890c11: Container 986a4d890c118922fd18a8ce1f12091e7917dcb47ea06253b9d1fd2c0f57b357 is not running
No resources found.
tput: unknown terminal "unknown"
tput: unknown terminal "unknown"
Cloning into 'bamboos'...
Cloning into 'cdmi_swagger'...
Cloning into 'one_env'...
Cloning into 'onepanel_swagger'...
Cloning into 'oneprovider_swagger'...
Cloning into 'onezone_swagger'...
Unable to use a TTY - container test-runner did not allocate one
If you don't see a command prompt, try pressing enter.
pod default/test-runner terminated (Error)
  % 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  3921  100  3921    0     0  15054      0 --:--:-- --:--:-- --:--:-- 15022
Error from server (NotFound): pods "dev-elasticsearch-data-0" not found
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container 99d8fb113c1f: Container 99d8fb113c1f2c6449db7114e180504d1367e9bc744445792a69e71738bbc42c is not running
Error response from daemon: Cannot kill container 2fc9673bb17a: Container 2fc9673bb17aae4d3a8cc30dca4a220aa6166a715c4f765c99fc77f92c820928 is not running
Error response from daemon: Cannot kill container 26b177995d27: Container 26b177995d27e835a30c68fcc72a1825b08f8a7162dbc565fdc30b156ada4f4d is not running
Error response from daemon: Cannot kill container 6c4c1bf3d5e3: Container 6c4c1bf3d5e32e5500932afc20ef1d81872966b218313674529c7da47c967b5b is not running
Error response from daemon: Cannot kill container f90cd1c606f7: Container f90cd1c606f72b22e39899e5c75ef346f2c3332dc06fc21918b026541388ed11 is not running
Error response from daemon: Cannot kill container faddce488e80: Container faddce488e808e7e94f4d2eade441807c58a5786fc15305223e8bcc4d895360a is not running
Error response from daemon: Cannot kill container f6c505c69292: Container f6c505c69292955fdfeae80eaffc330db4019856e3876874f51e37960abfbd07 is not running
Error response from daemon: Cannot kill container 0897a2f1eb88: Container 0897a2f1eb888f623cec99bd7bfa5537fdbd8f846c138d73c2ffab403305472f is not running
Error response from daemon: Cannot kill container 4ca3aba42e68: Container 4ca3aba42e68b57062a82968d6a9b930471b20094611e85c70d1aa6486d39732 is not running
Error response from daemon: Cannot kill container 07631bbf4787: Container 07631bbf478715717c0f64a0dc23687e8e6df70f930df60ce778a7c9352e805e is not running
Error response from daemon: Cannot kill container 6d8e8a354921: Container 6d8e8a3549211d1163e2b91254293e315bd272e4280370689febc2b15a778c78 is not running
Error response from daemon: Cannot kill container 767f0c7ab7d3: Container 767f0c7ab7d3a36b5f2b739628427c3e644c58958c7b9a1fb5c8a36f50ad633e is not running
Error response from daemon: Cannot kill container 2e9b66e633d9: Container 2e9b66e633d9f12c354d3d8684af9d5e60915571ca842a5f75ee3ca11d4f5a31 is not running
Error response from daemon: Cannot kill container 6a3e3b4aaadd: Container 6a3e3b4aaadd6213da203bdca693657b8f99ad66d3f046560791a63e29c3a066 is not running
Error response from daemon: Cannot kill container dd84b3ab330b: Container dd84b3ab330b054d4ba939da0ed863436cb17647e0ee057e781e0954b0be1b6f is not running
Error response from daemon: Cannot kill container f6e4c9abb4c3: Container f6e4c9abb4c3c96ef1e0c28608044338f4d7dd133a446b1d6af5b1f27e30c076 is not running
Error response from daemon: Cannot kill container 87efca5876c3: Container 87efca5876c38d04287e58459748ba62f09b0ab11f9a8604a0b542cb1e8dc42c is not running
Error response from daemon: Cannot kill container effde548fa7b: Container effde548fa7b2a09a7bae4501155f5796cc5d9d48d03fc16ffd61e0ce16a9c14 is not running
Error response from daemon: Cannot kill container f1ca7a1cdb13: Container f1ca7a1cdb136020d9b4aa132a277b7c7e3df48c0c56032042d673acf2c61f06 is not running
Error response from daemon: Cannot kill container 5c836dbdc3b6: Container 5c836dbdc3b61d1ff17a1a3cc8b3e21917665d1d1087e918464049a345675362 is not running