Post-install checks¶
DataRobot provides an automated Post-Install Checks Notebook to validate key features of your installation. The notebook is created automatically after each installation or upgrade—no manual setup is required. On each upgrade, the previous notebook is replaced with a fresh version that reflects the latest checks.
Overview¶
The notebook runs a series of checks to verify core platform functionality and, when available, optional features. Each check is an independent cell in the notebook that you can run individually or in sequence.
The following checks are included:
| Check | Description |
|---|---|
| Create project, predictions, and deploy model | Validates the core ML workflow: uploading data, training a model, generating predictions, and deploying. |
| GenAI pings | Verifies connectivity to GenAI infrastructure services. |
| Custom apps | Creates and deploys a custom application to confirm the feature is operational. |
| Custom models | Builds and deploys a custom inference model and tests predictions through it. |
| Workload API | Validates the Workload API by creating and running a containerized workload. |
Optional feature checks
Checks for optional features (GenAI, Custom Apps, Custom Models, Workload API) are skipped if the feature is not enabled in your installation.
Getting started¶
Note
The Post-Install Tests use case and notebook are created in the admin@datarobot.com account. Log in as that user to access them.
- After installation or upgrade, navigate to Use Cases in the DataRobot UI.
- Open the Post-Install Tests use case.
- Open the Post-Install Test Notebook.
- Review the first cell of the notebook. It contains usage instructions and prerequisites for running the checks.
Running the checks¶
Click Run on each cell individually, or select Run All to execute all checks in sequence. You can also run only the checks relevant to the features you want to verify.
Each check outputs its progress and results directly in the notebook, making it easy to identify any issues.
Remove temporary resources
After each execution, execute the Run Cleanup cell at the end of the notebook. The code in this cell removes all temporary resources (datasets, projects, deployments, and other artifacts) created during the checks and keeps your environment clean.