databricks.sdk.errors.platform.NotFound: [TABLE_OR_VIEW_NOT_FOUND] The table or view `hive_metastore`.`ucx_841570839244994`.`tables` cannot be found. Verify the spelling and correctness of the schema and catalog.
If you did not qualify the name with a schema, verify the current_schema() output, or qualify the name with the correct schema and catalog.
To tolerate the error on drop use DROP VIEW IF EXISTS or DROP TABLE IF EXISTS. SQLSTATE: 42P01; line 1 pos 14
[gw0] linux -- Python 3.10.20 /home/runner/work/ucx/ucx/.venv/bin/python
06:37 WARNING [databricks.sdk] Failed to get token for subscription. Using resource only token.
06:37 WARNING [databricks.labs.ucx.account.workspaces] User cannot access workspace: adb-4045495039142306.6
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1052, in __call__
header_factory = provider(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 95, in wrapper
return func(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 882, in metadata_service
token_source.token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 260, in token
return self._blocking_token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 307, in _blocking_token
self._token = self.refresh()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 863, in refresh
raise ValueError("Metadata Service returned empty token")
ValueError: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1059, in __call__
raise ValueError(f"{auth_type}: {e}") from e
ValueError: metadata-service: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 45, in client_for
return self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: metadata-service: Metadata Service returned empty token
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1061, in __call__
raise ValueError(
ValueError: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 52, in client_for
ws = self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 214, in can_administer
ws = self.client_for(workspace)
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 54, in client_for
raise PermissionDenied(f"Failed to create client for {workspace.deployment_name}: {exc}") from exc
databricks.sdk.errors.platform.PermissionDenied: Failed to create client for adb-4045495039142306.6: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
06:37 WARNING [databricks.sdk] Failed to get token for subscription. Using resource only token.
06:37 WARNING [databricks.labs.ucx.account.workspaces] User cannot access workspace: adb-7342989205138882.2
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1052, in __call__
header_factory = provider(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 95, in wrapper
return func(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 882, in metadata_service
token_source.token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 260, in token
return self._blocking_token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 307, in _blocking_token
self._token = self.refresh()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 863, in refresh
raise ValueError("Metadata Service returned empty token")
ValueError: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1059, in __call__
raise ValueError(f"{auth_type}: {e}") from e
ValueError: metadata-service: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 45, in client_for
return self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: metadata-service: Metadata Service returned empty token
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1061, in __call__
raise ValueError(
ValueError: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 52, in client_for
ws = self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 214, in can_administer
ws = self.client_for(workspace)
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 54, in client_for
raise PermissionDenied(f"Failed to create client for {workspace.deployment_name}: {exc}") from exc
databricks.sdk.errors.platform.PermissionDenied: Failed to create client for adb-7342989205138882.2: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
06:37 WARNING [databricks.sdk] Failed to get token for subscription. Using resource only token.
06:37 WARNING [databricks.labs.ucx.account.workspaces] User cannot access workspace: adb-4045495039142306.6
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1052, in __call__
header_factory = provider(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 95, in wrapper
return func(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 882, in metadata_service
token_source.token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 260, in token
return self._blocking_token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 307, in _blocking_token
self._token = self.refresh()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 863, in refresh
raise ValueError("Metadata Service returned empty token")
ValueError: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1059, in __call__
raise ValueError(f"{auth_type}: {e}") from e
ValueError: metadata-service: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 45, in client_for
return self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: metadata-service: Metadata Service returned empty token
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1061, in __call__
raise ValueError(
ValueError: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 52, in client_for
ws = self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 214, in can_administer
ws = self.client_for(workspace)
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 54, in client_for
raise PermissionDenied(f"Failed to create client for {workspace.deployment_name}: {exc}") from exc
databricks.sdk.errors.platform.PermissionDenied: Failed to create client for adb-4045495039142306.6: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
06:37 WARNING [databricks.sdk] Failed to get token for subscription. Using resource only token.
06:37 WARNING [databricks.labs.ucx.account.workspaces] User cannot access workspace: adb-7342989205138882.2
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1052, in __call__
header_factory = provider(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 95, in wrapper
return func(cfg)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 882, in metadata_service
token_source.token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 260, in token
return self._blocking_token()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/oauth.py", line 307, in _blocking_token
self._token = self.refresh()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 863, in refresh
raise ValueError("Metadata Service returned empty token")
ValueError: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1059, in __call__
raise ValueError(f"{auth_type}: {e}") from e
ValueError: metadata-service: Metadata Service returned empty token
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 45, in client_for
return self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: metadata-service: Metadata Service returned empty token
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 520, in init_auth
self._header_factory = self._credentials_strategy(self)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/credentials_provider.py", line 1061, in __call__
raise ValueError(
ValueError: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 52, in client_for
ws = self._ac.get_workspace_client(workspace)
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/__init__.py", line 1196, in get_workspace_client
config.init_auth()
File "/home/runner/work/ucx/ucx/.venv/lib/python3.10/site-packages/databricks/sdk/config.py", line 525, in init_auth
raise ValueError(f"{self._credentials_strategy.auth_type()} auth: {e}") from e
ValueError: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 214, in can_administer
ws = self.client_for(workspace)
File "/home/runner/work/ucx/ucx/src/databricks/labs/ucx/account/workspaces.py", line 54, in client_for
raise PermissionDenied(f"Failed to create client for {workspace.deployment_name}: {exc}") from exc
databricks.sdk.errors.platform.PermissionDenied: Failed to create client for adb-7342989205138882.2: metadata-service auth: cannot configure TEST_SCHEMA credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method.
[gw0] linux -- Python 3.10.20 /home/runner/work/ucx/ucx/.venv/bin/python
❌ test_account_aggregate_finds_no_overlapping_tables: databricks.sdk.errors.platform.NotFound: [TABLE_OR_VIEW_NOT_FOUND] The table or view `hive_metastore`.`ucx_841570839244994`.`tables` cannot be found. Verify the spelling and correctness of the schema and catalog. (11.04s)
Running from nightly #898