> ## Documentation Index
> Fetch the complete documentation index at: https://dpos.xdr.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# Post-Upgrade Validation

> Validate Ubuntu 24.04, DP 6.6.0, cluster readiness, services, and the final operator state.

# 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

```bash theme={null}
cat /etc/os-release
uname -r
```

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

## DP version and status

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

```text theme={null}
show version
show status
```

The current Mirror Manager target is **DP 6.6.0**.

## NTP and DNS

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

```bash theme={null}
timedatectl
systemctl is-active ntpsec systemd-timesyncd 2>/dev/null
```

When `ntpsec` is used:

```bash theme={null}
ntpq -p
```

Investigate an unsynchronized clock before returning the DP to service.

## Cluster nodes

For multi-node deployments:

```bash theme={null}
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.

## Application checks

At minimum verify:

* expected DP version is 6.6.0
* all expected nodes are ready
* required pods and host services are running
* DNS is configured
* NTP is synchronized
* licensing/OTP state is valid where applicable
* DL/DA role-specific services are healthy
* the Web UI and normal DP operations are reachable

## Logs and evidence

On the Mirror Server:

```bash theme={null}
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:

```text theme={null}
/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.