Skip to main content

​
5. Post-Upgrade Validation

Do not close the maintenance window just because the last upgrade command returned successfully. Validate the operating system and the DP application state.

​
1 — Verify Ubuntu on every DP node

Run:
Confirm every upgraded target node is running Ubuntu 24.04 and the expected kernel.

​
2 — Verify DP version and status

Enter the DP CLI and run:
The expected application target for the current Mirror Manager workflow is:
Do not treat a node as complete while show status still reports missing required services, unready nodes, or a non-ready role state.

​
3 — Verify DL/DA cluster readiness

For clustered deployments, confirm every expected node is present and Ready:
Validate:
  • DL master and all configured DL workers
  • DA master and all configured DA workers
  • release-specific labels and cluster networking where required
  • all expected pods and host services
The DL cluster should already have been validated before DA bringup began; this final check confirms the combined production state.

​
4 — Verify NTP and DNS

Check time synchronization:
When ntpsec is used:
Investigate an unsynchronized clock before returning the DP to service. Also confirm DNS resolution and the customer-required network paths.

​
5 — Verify application readiness

At minimum confirm:
  • DP version is 6.6.0
  • all expected nodes are Ready
  • required pods are running
  • required host services are ready
  • DNS is configured
  • NTP is synchronized
  • licensing/OTP state is valid where applicable
  • DL/DA role-specific services are healthy
  • Web UI and normal DP operations are reachable
Allow several minutes after resume for the platform to settle before deciding that a service is missing.

​
6 — Preserve evidence

On the Mirror Server, preserve the current status and logs:
On each DP that performed Phase 1, preserve:
Do not delete failure or state evidence when escalating a problem.

​
7 — Recovery snapshot cleanup

Keep the pre-upgrade/recovery snapshot until:
  1. Ubuntu 24.04 is confirmed on every required node
  2. DP 6.6.0 is confirmed
  3. DL and DA clusters are healthy
  4. NTP/DNS and application checks pass
  5. the maintenance/change procedure is approved for closure
Do not delete the recovery snapshot simply because the upgrade script returned success. Snapshot cleanup is the final action after technical validation and change-control approval.
When cleanup is approved, open the hypervisor snapshot manager for the DP VM.
Open VMware Manage Snapshots for the upgraded DP

Example: open the VMware snapshot manager

Select the temporary pre-upgrade snapshot and choose Delete snapshot.
Select the temporary DP upgrade snapshot for deletion

Example: select the temporary pre-upgrade snapshot for deletion

Confirm the deletion only after the approved validation gate has passed.
Confirm deletion of the temporary DP upgrade snapshot

Example: confirm snapshot deletion

Finally, confirm the temporary snapshot no longer appears in the snapshot manager.
VMware snapshot manager after temporary snapshot cleanup

Example: snapshot cleanup complete

​
Final completion checklist

  • Ubuntu 24.04 on every target node
  • DP 6.6.0 on every required role
  • DL cluster Ready
  • DA cluster Ready
  • required pods and host services Ready
  • NTP synchronized
  • DNS/network checks pass
  • license/OTP valid where applicable
  • Web UI and normal operations verified
  • upgrade logs/evidence preserved
  • snapshot cleanup approved or deferred per policy
When every required item is complete, the maintenance window can be closed. For lower-level checks, see Detailed Post-Upgrade Validation.