-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]:UCX Installation Failure #3330
Comments
Hello @Mbaroudi |
Hello @Trifa01 , |
Please find attached my debug and faked log for sensitive data: |
I have a similar issue, so I tried rolling back versions and could install |
Is there an existing issue for this?
Current Behavior
The
databricks labs install ucx
command fails during the installation process with aJSONDecodeError
. The error appears to occur when the installer attempts to parse an API response. This results in the installation process terminating unexpectedly.Relevant log output:
09:42:06 INFO [d.l.ucx.install] Installing UCX v0.50.0 Traceback (most recent call last): File "/path/to/requests/models.py", line 974, in json return complexjson.loads(self.text, **kwargs) File "/path/to/json/init.py", line 346, in loads return _default_decoder.decode(s) ... requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/path/to/databricks/labs/ucx/install.py", line 927, in workspace_installer.run() File "/path/to/databricks/labs/ucx/install.py", line 193, in run config = self.configure(default_config) ... requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0) Error: installer: exit status 1
Expected Behavior
The
databricks labs install ucx
command should successfully complete the installation of UCX in the Databricks environment, without errors or interruptions.Steps To Reproduce
3.10.15
(installed via Homebrew)Cloud
GCP
Operating System
macOS
Version
latest via Databricks CLI
Relevant log output
The text was updated successfully, but these errors were encountered: