Datadog Agent rollback lacks guarantee for post‑upgrade configuration preservation

Datadog Agent rollback does not guarantee preservation of configuration files that were modified after the last successful upgrade.

The rollback command requires the 'Datadog Agent: Manage' permission, yet it is unclear whether this permission covers scenarios where the previous agent version is not cached locally, and a file lock left unreleased by a crash can cause the rollback to hang.

Consequently, teams must verify that the agent returns to the prior version and that custom integrations remain functional, but the documentation does not specify how to confirm full configuration restoration.

Does the rollback command automatically restore all custom configuration files when the previous agent binary is not present locally? Is the 'Datadog Agent: Manage' permission sufficient for rollbacks that involve a missing cached version? Can a rollback be performed safely without a system reboot when the agent remains in an inconsistent state after a failed upgrade?