Post-Upgrade Validation

Do not close the maintenance window when the last command merely exits successfully. Validate both the operating system and the DP application state.

Operating system

cat /etc/os-release
uname -r

Confirm the node is running Ubuntu 24.04 and the expected kernel.

From the DP CLI, verify the target release and platform state:

show version
show status

The current Mirror Manager target is DP 6.6.0.

Validate time synchronization and DNS after the upgrade. Use the commands appropriate to the DP build, for example:

timedatectl
systemctl is-active ntpsec systemd-timesyncd 2>/dev/null

When ntpsec is used:

ntpq -p

Investigate an unsynchronized clock before returning the DP to service.

For multi-node deployments:

kubectl get nodes -o wide

Confirm every expected DL/DA master and worker is present and Ready, then verify release-specific labels and cluster networking.

At minimum verify:

On the Mirror Server:

ls -lt /var/log/ubuntu-mirror-automation/
cat /etc/ubuntu-mirror/dp-upgrade-mirror.status

On a DP performing Phase 1, preserve the upgrade evidence under:

/var/log/aella/auto_os_upgrade.log
/opt/aelladata/os-upgrade/

Investigate any warning, blocked state, failed check, or unexpected version before removing the pre-upgrade snapshot.