Domino 5.3.1 (October 2022)

Domino no longer becomes inaccessible after a fixed uptime period when running on Kubernetes 1.21 or higher.

You can now use periods in Snowflake data source account names.

Workspaces become unstoppable and their statuses don’t change when the timestamps on the run’s status changes array are incorrect.

After deleting branches that were created in GitHub but not pulled (that is, they are not local on Domino), they are still shown in the Code menu in the Data tab of the workspace.

In the Control Center’s navigation pane, click Assets. Domino displays a "Failed to get assets" message and takes a long time to load the assets.

In projects where the Environment variables and Files checkboxes are selected in the Exports settings, you might see a 500 page console error Failed to load resource when you create and save a new file.

If you use a forward slash (/) in a Git branch name, the forward slash and any preceding text is stripped. For example, if the branch was named test/branch1, it will be renamed branch1.

The graph views are skewed incorrectly, in Domino’s model monitoring, when normalized values are small. If you create a new GitLab repository during creation of a Git-based project, Domino shows the following message: Cannot create project because of Git repository creation failure - Credential does not have permission to create a repository. However, the repository is created. GitLab has a bug that causes this message. See Create a Git-based Project.

Upgrading to this release from Domino 3.x or 4.x can cause Git credentials to be omitted from the dropdown when creating a new Git-based project. A workaround is available from Domino’s Customer Success team.

When you use drag-and-drop to upload a large number of files at once, the upload might fail. The application displays many empty dialogs. Use the Domino CLI to upload large numbers of files instead. Domino 5.4.0 eliminates the empty dialogs and shows helpful information.

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.

A limit overcommit error (OOMKilled) is occurring frequently on the prometheus-adapter pod in Domino’s Integrated Model Monitoring. The current workaround is to increase the limits. This issue is resolved in Domino 5.5.0.

Runs might fail during startup with an error about a missing Kerberos environment variable. This issue is resolved in Domino 5.3.2.

Nucleus crashes when you go to Admin > Executions on a deployment with hundreds of executions. This issue is resolved in Domino 5.3.2.

When a practitioner user attempts to update a project forked from another after the source project has been updated, a 403 Access Forbidden error is shown.

Domino Model Monitor is not compatible with Kubernetes versions 1.21 and above and stops working after 90 days of uptime. A periodic graceful restart of Domino Model Monitor is advised as a workaround. This issue is resolved in Domino 5.5.0.

If the Model Access Token Vault migration runs more than once, it wipes tokens from Mongo and Vault, and users need to regenerate their Model Access Tokens in the UI. This is fixed in Domino 5.4.0.

"Other" Git service provider URLs not ending in ".git" fail to work when you attempt to create a project from a Git repo or add a Git repo to a project. This issue is fixed in Domino 5.5.0.

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.

Configuring prediction when setting up prediction capture for model APIs causes predictions to not be captured. This issue is resolved in 5.4.0.

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.

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.