About Domino
Domino Data LabKnowledge BaseData Science BlogTraining

Domino 5.5.1 (March 2023)

This release provides security patches, bug fixes, and improvements.

See also the fleetcommand-agent Release Notes.

Improvements

  • In-cluster docs for the Admin Toolkit

    • Documentation included within the Domino deployment: You can access the toolkit reference documentation specific to your deployed version by navigating to https://<your-domino-url>/toolkit/docs/. This allows you to reference the most relevant documentation for your specific Domino environment.

    • Publicly-accessible online documentation updates: You can now access the latest version of the toolkit check documentation at https://docs.toolkit.re.domino.tech/. This ensures that you always have access to the most up-to-date information about the toolkit and its checks.

    • Improved toolkit check documentation: The reference documentation provides more comprehensive information about checks and guidance on resolving issues so that you can quickly identify and address problems, ensuring optimal performance of the Domino platform.

Bug fixes

  • There is no longer an intermittent inability to schedule DMM jobs. The memory leak in the DMM scheduler has been fixed.

Known issues

  • You cannot view the latest raw file. In the navigation pane, go to Files and click a file to view its details. If you click View Latest Raw File, a blank page opens.

  • When uploading a large file to the Azure blob store by syncing a workspace, you may encounter a Java Out of Memory error from Azure if the file/blob already exists. To work around this issue, use the Domino CLI to upload the file to the project.

  • Model Monitoring data sources aren’t validated. If you enter an invalid bucket name and attempt to save, the entry will go through. However, you won’t be able to see metrics for that entry because the name points to an invalid bucket.

  • In Azure Blob Store deployments, projects with many files may fail to sync through the Domino CLI. To work around this issue, do not disable file locking when prompted by Domino.

  • Domino instances that make use of Azure Blob Storage may experience stalled jobs within projects with many large files.

  • When using Azure Blob Storage for backups, daily backups do not complete successfully and backups are only stored in Azure Files storage. This issue is resolved in Domino 5.6.1.

  • Upgrading Domino from a version below 5.5.0 to version 5.5.1 on Azure AFS may fail if the Keycloak script providers were previously configured on your instance. Contact Domino Support for help. This issue is resolved in Domino 5.7.0.

  • Publishing a new version of a model API as a non-admin user fails if the first model in the project was created by someone else. To address this problem, add the non-admin user as a collaborator to the prediction_data dataset for that project. This issue is fixed in Domino 5.5.4.

  • If the nucleus-dispatcher Kubernetes pod is restarted (during Domino upgrade, after restarting Nucleus services via the admin central configuration page, after the previous pod crashing, or for some other reason), then existing executions (including workspaces and jobs) may fail. This issue is resolved in Domino 5.5.4.

  • The Status, Active Version, and Owner columns do not appear in the Model API list. This issue is fixed in Domino 5.8.0.

  • Deleting all R variables from memory using rm(list = ls(al = TRUE)) also deletes variables that Domino uses for internal processes. To safely delete variables, use rm(list = ls(all = TRUE)[!grepl("^.domino", ls(all = TRUE))]) instead."

  • When restarting a Workspace through the Update Settings modal, External Data Volumes are not mounted in the new Workspace. Follow the steps to mount External Data Volumes. This issue is fixed in Domino 5.9.0.

  • Downloading single files from Datasets will fail if the filename contains special characters, including + and &. As a workaround, remove the mentioned special characters by renaming the file. This issue is fixed in Domino 5.10.0.

  • Spaces in ADLS filenames are not allowed when getting and putting objects in Azure Data Sources with DominoDataR. As a workaround, upgrade to DominoDataR version 0.2.4. This issue is fixed in Domino 5.10.0.

  • Viewing dataset files in an Azure-based Domino cluster may lock files, preventing them from being deleted or modified. Restarting Nucleus frontend pods will release the lock. This issue is fixed in Domino 5.11.1.

Upgrade notes

Important
 If you are upgrading to this Domino release from a version earlier than Domino 5.3.0, you must put Domino into maintenance mode to avoid losing work. Maintenance mode pauses all apps, model APIs, restartable workspaces, and scheduled jobs. Allow running jobs to complete or stop them manually.