...
Cloudaware generates a patching snapshot defining the patches and their versions to which they will be updated. Cloudaware guarantees that this snapshot to be implemented across all environments such as Dev, QA, Staging and Prod. If any patch is detected as manually upgraded or auto-installed, Cloudaware will skip it.
The Cloudaware patch process also supports patch groups, meaning that only members of one patch group will be rebooted at a time if necessary.
Rollback Mechanism
Rollback To undo a failed patch release, customers can address Cloudaware's rollback script available by default. Cloudaware can perform a simultaneous rollback in all instances within a given cloud account.
The rollback script is located on every patched instance in the following location: /opt/breeze-agent/os_updater/YYYYMMDDhhmmss.sh
If rollback is requested, Cloudaware’s Breeze agent will set repo to the previous GUID, execute the rollback script and verify rollback using yum update against preview repo GUID. After the script execution is complete, the yum update should not introduce any changes to the packages on the host.
...