Known issues in 1.5.5 SP1

You might run into some known issues while using Cloudera AI on premises.

Cloudera AI on premises 1.5.5 existing known issues are carried into Cloudera AI on premises 1.5.5 SP1. For more details, see Known issues for Cloudera AI on premises 1.5.5. For known issues fixed since Cloudera AI on premises 1.5.5, see Fixed issues in 1.5.5 SP1.

DSE-47608: Update Hive on Base to use the correct SSL configuration value

SSL is always set to true when discovering the Hive on TEZ data connection, regardless of whether SSL is enabled.

Workaround:

As a workaround, the JDBC URL can be modified by editing the data connection settings.

DSE-47480: MLUsers are able to delete other users' deployed endpoints

Cloudera AI Inference service lacks fine-grained authorization, allowing endpoints created by one user to be deleted by another user.

DSE-47517: Parallel backup or restore during other ongoing Platform actions ends up workbench in failed state

Backup and restore actions lack validation checks for ongoing platform actions, leading to conflicts when triggered simultaneously with other platform actions.

No workaround exists for this issue. However, Cloudera recommends avoiding the initiation of any other workbench actions while a platform action is in progress on the same workbench.

DSE-46826: Registry upgrade is incorrectly returning 500 even though upgrade flow is being triggered

The registry upgrade process returns an HTTP 500 error in the UI and CLI, despite successfully completing in the background. The issue is linked to missing records and Docker secrets, likely due to recent changes in secrets handling.

Workaround:

Recreating the Cloudera AI Registry with valid Ozone credentials resolves the error and ensures that the upgrade completes successfully.

DSE-47916: Update storage configuration option overwrites the S3 Region parameter

The S3 Region parameter with an empty value overwrites the existing s3Region value when using the Update storage configuration option in the UI or the updateMlServingAppS3Creds API. This causes model deployment failures, as updating only the mandatory fields clears the s3Region value, leading to authorization errors.

Workaround:

Always include the S3 Region parameter when using either the updateMlServingAppS3Creds API or the Update storage configuration option in the UI.

DSE-47973: Update Storage Configuration disabled in Update Creds failed state

If the credentials update fails, the S3 storage configuration cannot be updated. Additionally, the UI does not display a warning to inform the user that the S3 storage configuration has been disabled.