After the upgrade is done, you will be redirected back to the login page.
Log in to Delphix Setup to verify that the upgrade succeeded and the new version is running.
A post-upgrade cleanup job is run automatically after the upgrade is done. This job refreshes environments and re-enables sources to bring objects back into a working state. After an Upgrade and Reboot, access to VDBs disabled for the reboot remains unavailable until the environments have been refreshed and the objects are re-enabled by the job Perform cleanup tasks following a Delphix engine upgrade. An Upgrade Only does not interrupt VDB access.
After a successful upgrade, Setup displays a Success banner with the message “Engine has been upgraded.”
After an Upgrade and Reboot, Setup also displays a Success banner with the message “Engine upgrade finalized via successful reboot.”
Failures
If you used Continue upgrade to force the upgrade as is described in Failure to quiesce a dataset, the Report tab will contain the list of pre-upgrade quiesce failures. Upgrade will make a best effort to restore functionality to these datasets, but it may still hit the same errors that prevented the datasets from being quiesced successfully before the upgrade. You may need to manually bring up these datasets on the target hosts.
Finalize upgrade
If you selected Upgrade Only and the upgrade includes fixes requiring a reboot, a Finalize Upgrade button will appear after logging into the Delphix Setup application. The software is already installed. Finalize Upgrade stops running jobs, temporarily pauses VDBs and dSource updates, and reboots the engine to activate those fixes. After the reboot, normal operations resume.
Reset integrity boot measurements for GCP Shielded VM
On GCP Shielded VMs with virtual Trusted Platform Module (vTPM) and Integrity Measurement Architecture (IMA) enabled, engine upgrades may introduce a new kernel image and/or bootloader, which can trigger lateBootReportEvent alerts on subsequent boots. You can view these alerts in the GCP Console under VM > Observability > Logs. To accept the updated boot components as the new trusted baseline, run the following command:
gcloud compute instances update INSTANCE_NAME --zone=ZONE \
--shielded-learn-integrity-policyThis command generates a SetShieldedInstanceIntegrityPolicy event and records the current boot measurements as trusted. After you run the command, subsequent reboots no longer produce lateBootReportEvent alerts, confirming the upgraded system components are recognized as trusted.