Domino 4.6.1 (October 2021)

See also the fleetcommand-agent Release Notes.

Upgrades & Enhancements

Model audit logging is improved in this release, with more model events written to the application logs. See Audit logging in the Administration Guide for details.

Bug Fixes

Empty directories no longer appear after importing a project or a git repo and then restarting the workspace.
Snapshots no longer hang when triggered inside a subfolder.
Shared datasets are now grayed out for users without access to them.
This release addresses an issue where dataset snapshots were incomplete if initiated from a folder other than the root of the dataset.

Known issues

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

When upgrading from Domino 4.x to 5.1, Domino does not correctly handle environment revisions that have both a Docker image and a base environment revision. This issue is resolved in Domino 5.2.0.

Note
When upgrading from Domino 4.x to 5.1, contact Domino’s Customer Success team for access to the migration script that provides a workaround for this issue.

Apps may fail with unusual error messages. This issue is resolved in Domino 5.2.0.

Opening an un-cached workspace can cause the workspace to get stuck in the "Pulling" status. This is fixed in Domino 4.6.4.

When an API key explicitly passed as an api_key argument and the DOMINO_TOKEN_FILE environment variable is set, Domino uses the token authentication. This issue is resolved in Domino 5.2.0.

When Flask apps generate links, this can result in unwanted 302 redirect behavior. This issue is fixed in Domino 5.2.0.

When a Model API fails while retrieving files from git using SSH keys, the private key and the key password, if any, may be exposed in the Domino log. This issue is resolved in Domino 5.2.0.

The Import Project drop-down does not display projects owned by organizations of which you are a member. This issue is resolved in Domino 5.2.0.

When starting a workspace, the application sometimes gets stuck in the Pulling status, even though the logs indicate that the workspace started successfully. If this occurs, stop and start the workspace again. This issue is fixed in Domino 5.2.0.

In a Git-based project, requirements.txt must be in your project’s Artifacts folder in order to be picked up by an execution, instead of at the root level in your project files.

Tip
To avoid falling out of sync with the Git repository, always modify requirements.txt in the repository first and then copy it to your project’s Artifacts folder.

Domino can become inaccessible after a fixed uptime period when running on Kubernetes 1.21 or higher. See this knowledge base article for the workaround. This issue is fixed in Domino 5.3.1.

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.

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.