Known Issues
You might run into some known issues while using Cloudera Machine Learning on Private Cloud.
DSE-35013: First CML workspace creation fails
On RHEL 8.8, during the first CML workspace installation on GPU with ECS external registry, pods might get stuck in the init or crashloop state.
First-time workspace installation is expected to fail. Cloudera recommends that you
consider this as a test workspace, and apply the following manual workaround for creating
subsequent workspaces:
- Restart or delete the pods which are in init or crashloop state in the test workspace.
- Once all pods are in the running state, create new workspaces as needed.
- Delete the test workspace from the CML UI if no longer needed.
DSE-32887: Runtime Updates can not be enabled from the Site admin UI on Private Cloud Data Services
With this bug present on Private Cloud Data Services 1.5.2 and 1.5.3, Runtime repositories added on the Site Administration>Runtimes page will not be scanned for new Runtimes. Adding Runtime repositories to CML was a new feature in 1.5.2. Unfortunately with this bug, the feature is completely unusable.
Workaround: Manually enable Runtime updates with an API call using the legacy API key of
the admin user. That will let CML check the registered runtime registries for new runtimes
every 24 hours. The syntax of the API call is as
follows:
curl 'https://<CML_URL>/api/v1/site/config' \
-X 'PATCH' \
-u <ADMIN_APIv1_KEY>: \
-H 'content-type: application/json' \
-d '{"enable_runtime_updates":true}'DSE-32730: Workloads unable to start up after changing default hadoopCLI addon
Changing the default Hadoop CLI Runtime Addon causes jobs, models, and application workloads to be unable to start up.
Workarounds:
- Open affected workload settings.
- Update the workload (this updates the Hadoop CLI Addon associated with the workload to the default one.)
- For Jobs: update.
- For Applications: update and restart.
- For Models: deploy a new build.
