About Domino
Domino Data LabKnowledge BaseData Science BlogTraining

Domino 5.6.1 (June 2023)

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

See also the fleetcommand-agent Release Notes.

Improvement: Schedulable toolkit reports

Admin Toolkit v2 introduces these new features:

  • Regular report scheduling

    Now the toolkit can automatically run reports at regular intervals. This is useful for creating a "Healthy State" report that you can use as a comparative baseline for easier diagnosis of any operational issues. Use this feature to obtain timely insights and to minimize manual efforts in monitoring system health.

    See Scheduled reports for complete instructions.

  • Redis middle tier and backend worker containers

    The running of reports has been separated out from the frontend UI, improving the performance and stability of the toolkit.

See Upgrade from v1 to v2 to get this new version of the Admin Toolkit.

Bug fixes

  • When using Azure Blob Storage for backups, daily backups complete successfully and are uploaded to blob storage.

  • Users can see raw files whose size is ⇐ 5 MB (com.cerebro.domino.frontend.defaultMaxFileSizeToRenderInBytes) when they click on the "View Latest Raw File" button in the code file browser, even if their S3 buckets don’t have CORS enabled.

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.

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

  • Upgrading Domino from a version below 5.5.0 to version 5.6.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.

  • If you attach a Git repository to a DFS project that points to a tagged release, the tag won’t be honored when building a model API in that project. The build log will show an error similar to the following, and the model will be built using the default branch of your Git repository instead of the tagged branch:

    Jul 05 2023 14:36:27 -0500 #10 6.481 WARN [d.r.d.GitRepoUpdater] could not parse ref: v1.3.0 checking out default branch correlationId="iA2qWrYSLQ" thread="main"

    To work around this issue, use the branch name when building model APIs instead of the release tag.

  • 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.6.2.

  • 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
 Before you upgrade, 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.