GUI acceptance tests using environment deployed from packages.
Build: #2261 failed
Job: Onezone automations failed
user sees bagit metadata files and directory tree in aip tab and directory tree in dip tab in archive browser after creating archive with bagit layout and include dip option[1oz 1op deployed]: Test case result
The below summarizes the result of the test " user sees bagit metadata files and directory tree in aip tab and directory tree in dip tab in archive browser after creating archive with bagit layout and include dip option[1oz 1op deployed]" in build 2,261 of Onedata Products - gui acceptance pkg - Chrome oneprovider archives tests.
- Description
- user sees bagit metadata files and directory tree in aip tab and directory tree in dip tab in archive browser after creating archive with bagit layout and include dip option[1oz 1op deployed]
- Test class
- gui.scenarios.test_oneprovider_archives
- Method
- test_user_sees_bagit_metadata_files_and_directory_tree_in_aip_tab_and_directory_tree_in_dip_tab_in_archive_browser_after_creating_archive_with_bagit_layout_and_include_dip_option[1oz_1op_deployed]
- Jira Issue
-
- Duration
- 13 secs
- Status
- Failed (New Failure)
Error Log
tests.utils.http_exceptions.HTTPBadRequest: [400] Bad Request: {"error":{"id":"errorOnNodes","details":{"hostnames":["dev-oneprovider-krakow-0.dev-oneprovider-krakow.default.svc.cluster.local"],"error":{"id":"badValueToken","details":{"tokenError":{"id":"badToken","description":"Provided token could not be understood by the server."},"key":"token"},"description":"Bad value: provided \"token\" is not a valid token (see details)."}},"description":"Error on nodes dev-oneprovider-krakow-0.dev-oneprovider-krakow.default.svc.cluster.local: Bad value: provided \"token\" is not a valid token (see details)."}} request = <FixtureRequest for <Function 'test_user_sees_bagit_metadata_files_and_directory_tree_in_aip_tab_and_directory_tree_in_dip_tab_in_archive_browser_after_creating_archive_with_bagit_layout_and_include_dip_option[1oz_1op_deployed]'>> @pytest.mark.usefixtures(*function_args) def scenario_wrapper(request): > _execute_scenario(feature, scenario, request, encoding) /usr/local/lib/python3.6/dist-packages/pytest_bdd/scenario.py:227: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/local/lib/python3.6/dist-packages/pytest_bdd/scenario.py:189: in _execute_scenario _execute_step_function(request, scenario, step, step_func) /usr/local/lib/python3.6/dist-packages/pytest_bdd/scenario.py:130: in _execute_step_function step_func(**kwargs) /usr/local/lib/python3.6/dist-packages/pytest_bdd/steps.py:162: in step_func result = request.getfixturevalue(func.__name__) /usr/local/lib/python3.6/dist-packages/_pytest/fixtures.py:428: in getfixturevalue return self._get_active_fixturedef(argname).cached_result[0] /usr/local/lib/python3.6/dist-packages/_pytest/fixtures.py:453: in _get_active_fixturedef self._compute_fixture_value(fixturedef) /usr/local/lib/python3.6/dist-packages/_pytest/fixtures.py:524: in _compute_fixture_value fixturedef.execute(request=subrequest) /usr/local/lib/python3.6/dist-packages/_pytest/fixtures.py:795: in execute return hook.pytest_fixture_setup(fixturedef=self, request=request) /usr/local/lib/python3.6/dist-packages/pluggy/__init__.py:617: in __call__ return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) /usr/local/lib/python3.6/dist-packages/pluggy/__init__.py:222: in _hookexec return self._inner_hookexec(hook, methods, kwargs) /usr/local/lib/python3.6/dist-packages/pluggy/__init__.py:216: in <lambda> firstresult=hook.spec_opts.get('firstresult'), /usr/local/lib/python3.6/dist-packages/_pytest/fixtures.py:826: in pytest_fixture_setup result = call_fixture_func(fixturefunc, request, kwargs) /usr/local/lib/python3.6/dist-packages/_pytest/fixtures.py:718: in call_fixture_func res = fixturefunc(**kwargs) tests/utils/bdd_utils.py:78: in wrapper return fun(*ba.args, **ba.kwargs) tests/gui/steps/rest/env_up/spaces.py:104: in create_and_configure_spaces users, groups, storages, spaces) tests/gui/steps/rest/env_up/spaces.py:135: in _create_and_configure_spaces users_to_add, users_db) tests/gui/steps/rest/env_up/spaces.py:240: in _get_support data=json.dumps(space_support_details)) tests/utils/rest_utils.py:57: in http_post verify, cert, auth, data, default_headers=default_headers) tests/utils/rest_utils.py:85: in http_request raise_http_exception(response) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ response = <Response [400]> def raise_http_exception(response): ex_cls = _exceptions.get(response.status_code, HTTPError) > raise ex_cls(response) E tests.utils.http_exceptions.HTTPBadRequest: [400] Bad Request: {"error":{"id":"errorOnNodes","details":{"hostnames":["dev-oneprovider-krakow-0.dev-oneprovider-krakow.default.svc.cluster.local"],"error":{"id":"badValueToken","details":{"tokenError":{"id":"badToken","description":"Provided token could not be understood by the server."},"key":"token"},"description":"Bad value: provided \"token\" is not a valid token (see details)."}},"description":"Error on nodes dev-oneprovider-krakow-0.dev-oneprovider-krakow.default.svc.cluster.local: Bad value: provided \"token\" is not a valid token (see details)."}} tests/utils/http_exceptions.py:15: HTTPBadRequest