Domino 5.1.3 (May 2022)

This release provides security patches and these enhancements:

Compatibility with Kubernetes 1.21.

Handle invalid environment revisions

In Domino 5.0.0 through 5.1.2, Mongo records can have a Docker image or a base environment revision but not both. When upgrading from Domino 4.x to 5.1.3 and above, Domino uses the base environment revision to gracefully handle environment revisions that have both a Docker image and a base environment revision.

Note

Resolve Vault and Kubernetes 1.21 issue

In prior versions of Domino, there were Vault failure issues with Kubernetes 1.2.1. This issue is resolved in the 5.1.3 release.

Note

Known issues

The output of the gateway/runs/getByBatchId endpoint is missing the runs and nextBatchId objects. This issue is resolved in Domino 5.2.0.

When viewing a raw HTML file while com.cerebro.domino.frontend.allowHtmlFilesToRender is false, Javascript can be executed. This issue is fixed in Domino 5.2.0.

When you set an environment as the default on the Environments page and then restart the service, Domino reverts to the default environment previously set on the Central Configuration page. This issue is fixed in Domino 5.2.0.

Sync operations for deployments backed by SMB file stores can sometimes result in unintended file deletions. This issue is fixed in Domino 5.2.0.

You cannot delete a .gitignore file in a Domino File System (DFS)-based project. This issue is fixed in Domino 5.2.0.

Jobs can fail or become stuck in a Pending state when using files from an S3 data source. This issue is fixed in Domino 5.2.0.

Entering a URI in the New Environment window can cause the window to go blank. This issue is resolved in Domino 5.2.0.

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

The Domino UI may hang with a "Waiting for available socket" error. This issue is resolved in Domino 5.2.0.

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.

MATLAB environment builds may fail, or MATLAB workspaces may be unresponsive.

You might experience slow loading times when you open the Environments, Workspaces, Model APIs, or Projects pages.

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.

Setting com.cerebro.domino.workloadNotifications.isRequired to true does not prevent users from turning off notifications, and changing the value of com.cerebro.domino.workloadNotifications.maximumPeriodInSeconds has no effect.

When you add environment variables to a project, they are visible in the execution_specifications collection in MongoDB.

After upgrading to 4.6.4 or higher, launching a job from a Git-based project that uses a shared SSH key or personal access token results in a Cannot access Git repository error.