Nothing has changed on this front in 8.7.
Even redhat lists limitations to this:
Note: Downgrading a system to minor version (ex: RHEL6.1 to RHEL6.0) is not recommended as this might leave the system in broken state where libgcc and other libraries won't rollback as expected. Use the history option for small update rollbacks.
Note: Rollback of selinux, selinux-policy-*, kernel, glibc (dependencies of glibc such as gcc) packages to older version is not supported.
Most customers use vm snapshots before patching. maybe if redhat figures out how to integrate yum and btrfs snapshots they will have a more stable solution.
thanks for the update. in reading your URL link Red Hat does provide a process for Roll Back on version 6,7. is this something which BSA can incorporate?
also from Red Hat Support ; https://access.redhat.com/solutions/24942
- The recommended way to do a rollback is to use the Red Hat Network/Satellite provisioning module and snapshot capabilities.
- Snapshots are captured whenever an action takes place on a system. These snapshots identify groups, channels, packages, and configuration files.
maybe BSA can work with Satellite server for roll back?
2 of 2 people found this helpful
Anything is possible. right now we don’t have that functionality . you can create or vote up an ‘idea’ for this on the ideas section of this community. since there seems to be some question if redhat even recommends it, many of our customers will do a snapshot of the vm prior to any patching and use that for rollback rather than deal w/ any rpm rollback issues.