See also the fleetcommand-agent Release Notes.
-
Domino now generates short-lived JWT tokens that can be used to authenticate to third party resources, data sources, and the Domino API. Tokens are made available in Workspaces, Jobs, or Apps. Learn more about Domino’s JWT tokens.
-
All components of Domino On-demand Spark clusters are now displayed with key infrastructure and configuration information in the administrator’s execution dashboard.
Changes
-
fleetcommand-agentv25 released to support 4.3.0 installation. -
Domino now uses version 10.0.1 of Keycloak.
-
Domino now uses version 7.7.1 of Elasticsearch.
-
Fixed an issue that prevented hardware tiers from functioning as intended if the Cores Limit field was left blank. Execution specifications would still be produced with a limit equal to the CPU request. Now, leaving the Cores Limit field blank will correctly produce execution specifications with no CPU limit.
-
Fixed an issue that prevented GPU-based Spark clusters from functioning properly.
-
Fixed an issue where restarting a node would cause apps in Domino to fail.
-
Fixed an issue that prevented workspaces from properly detecting file changes when performing volume recovery.
-
Fixed an issue that prevented workspace recovery with a salvaged volume if a Domino session was expired.
-
Fixed an issue where the base image in an Environment changed when other non-image changes were made to the Environment.
-
Fixed an issue that prevented archived workspaces and jobs from appearing in their corresponding dashboard.
-
A pending Domino Workspace prematurely reports the progress as Running and is stuck there for a long time before it is actually running.
-
Models have long queueing times when handling multiple simultaneous queries.
-
The error messaging is unclear when there is an environment build failure due to Dockerfile parsing errors.
-
There is a spike in requests when using the getLogsWithProblemSuggestions endpoint to fetch logs for failed jobs, which is causing some pods to run out of memory.
-
Sorting by the Collaborators column on the Projects Portfolio page of Control Center does not work.
-
Model API Settings page is crashing when there are empty environment variables in models.
-
Domino CLI is logging raw HTML for certain errors.
-
When using the Domino Minimal Distribution (DMD), it fails to install some dependencies.
-
Domino workspaces and runs cannot be stopped from the Domino app.
-
When committing to a protected branch, the push succeeds without errors or pending changes.
-
Domino shows an incorrect number of Spark executors when launching a workspace with a Spark cluster even though the correct number of Spark executors were allocated to the workspace.
-
If you go to download a revision for an environment from another user and click Download Image Source Project, a 403 error will occur.
-
A pagination issue causes search results to display with empty pages in the Environments dashboard.
-
The search in the Environments dashboard returns an empty table if the name of the environment contains special characters.
-
If you use the API to export a model in a Sagemaker compliant image, and then try to deploy that model as an endpoint in Sagemaker, the system will throw an error.
-
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.