Build #648

Plan branch:
GUI acceptance tests using environment deployed from packages.

Build: #648 failed

Job: Chrome metadata test failed

Job result summary

Completed
Duration
28 minutes
Revision
1250895e54287fb5b835eb62f6db05eaf6d1f7f1
Total tests
27
Failing since
#646 (Child of ODSRV-OZP-1253 – )
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
  • 20 minutes taken in total.
Existing test failures 27
Status Test Failing since Duration 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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...)
 
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  14098      0 --:--:-- --:--:-- --:--:-- 14104
Error response from daemon: Cannot kill container be1ce9f32664: Container be1ce9f32664e67106da96b55713856e1cc287a87d188d131a5b095eea44600a 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:00:01 --:--:--     0
100  3921  100  3921    0     0   2344      0  0:00:01  0:00:01 --:--:--  2345
Error from server (NotFound): pods "dev-elasticsearch-master-0" not found
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container 5686fba52872: Container 5686fba52872816a8684b6ca64c300448e4fa64569dda86289a7a35008093c57 is not running
Error response from daemon: Cannot kill container 2cfc71143ec4: Container 2cfc71143ec4b92d2cf816e23353567526074060330114688fc7bfa1c53bd85e is not running
Error response from daemon: Cannot kill container ffa7fd625cb9: Container ffa7fd625cb9f042c22a0dde71fc993b5767874f658fbc7e29cc33e43132e762 is not running
Error response from daemon: Cannot kill container 4ae9fc445b3f: Container 4ae9fc445b3f3636fe23f617865a0205746db8566c500e4ac3ecb087bafbeb0c is not running
Error response from daemon: Cannot kill container 592ce2a7abb5: Container 592ce2a7abb576686f2516256bec2c10d9b5a2942508362abda626526e012a27 is not running
Error response from daemon: Cannot kill container 0ecce93973a6: Container 0ecce93973a6cc690247b9dc21d5957d13498ffbc4a8d353f6650c9c8f7b2d66 is not running
Error response from daemon: Cannot kill container c98ffcbf15ab: Container c98ffcbf15ab0f1e0140d8331d9baa797311806f35ccc80f6b7c8de64020ce34 is not running
Error response from daemon: Cannot kill container b83f7ed3b61a: Container b83f7ed3b61a13318291683066f8ce2622b50cb482b9357b463ca5b0a477a349 is not running
Error response from daemon: Cannot kill container f72f10cf179a: Container f72f10cf179af96fa53a37bfb19e894ab12e0a1f73e1311dcba3d9f1f049b977 is not running
Error response from daemon: Cannot kill container e10e89cbd1ca: Container e10e89cbd1cac72e8bf2962d93c8a332f608e803bb047e34600b2e3ef216bf04 is not running
Error response from daemon: Cannot kill container a71699e58177: Container a71699e58177e26ea6f98fa3a72fa87e98d03258d237765f77540790ec775a67 is not running
Error response from daemon: Cannot kill container 73548e23f2ea: Container 73548e23f2ea8c3e0a3b263aa45b481785c86586b4635d0666920c4c547cf25b is not running
Error response from daemon: Cannot kill container 39e881242db7: Container 39e881242db73b436bfe58b7f9880c62a01ca4cded8f582fdfd8acb2ab37264a is not running
Error response from daemon: Cannot kill container ac99c27406c0: Container ac99c27406c01e76164bdfa1ff92574d72e396398561206260fe6d29dc6af314 is not running
Error response from daemon: Cannot kill container 44105e21fe06: Container 44105e21fe068c653aa3602aefbfc85664f1ad879ffb0532e1ec1af4dfb44206 is not running
Error response from daemon: Cannot kill container 7c37c60f0a26: Container 7c37c60f0a26640e0e1aa92129ae494ff48ee15b68ae3c6c832aaca1287b5e7c is not running
Error response from daemon: Cannot kill container 6bc4b05eb3c3: Container 6bc4b05eb3c33953921da31dab93b215e51f51196539b3523863f2776ea78714 is not running
Error response from daemon: Cannot kill container 2574b65021d4: Container 2574b65021d45035e4fd9e54e719bd7329d61547c0c86074ae21c9b706cbc54a is not running
Error response from daemon: Cannot kill container 699eaed8f87d: Container 699eaed8f87d7535f395eb4280bd8b34ae8d8624577a1857f71f014567dd7211 is not running
Error response from daemon: Cannot kill container 5a713b00f842: Container 5a713b00f8429660dc8dc05b904d895d2cb5d21c160c994a1f017548dc2bd660 is not running