Centos Yum history undo

• How to use yum history to roll back an update in Red Hat Enterprise Linux 6 , 7?

yum history

yum history undo 8

[root@devadmin jenkins]# yum history undo 298
Loaded plugins: fastestmirror, priorities, refresh-packagekit, security
Undoing transaction 298, from Tue Apr 11 14:21:00 2017
    Updated jenkins-2.53-1.1.noarch @jenkins
    Update          2.54-1.1.noarch @jenkins
Loading mirror speeds from cached hostfile
 * atomic: mirrors.thzhost.com
 * base: mirror.oasis.onnetcorp.com
 * epel: mirror.premi.st
 * extras: mirror.oasis.onnetcorp.com
 * jpackage: ftp.heanet.ie
 * remi-safe: ca.mirror.babylon.network
 * rpmforge: ftp.kddilabs.jp
 * updates: mirror.oasis.onnetcorp.com
239 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package jenkins.noarch 0:2.53-1.1 will be a downgrade
---> Package jenkins.noarch 0:2.54-1.1 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================================================================================
 Package                                    Arch                                      Version                                     Repository                                  Size
===================================================================================================================================================================================
Downgrading:
 jenkins                                    noarch                                    2.53-1.1                                    jenkins                                     65 M

Transaction Summary
===================================================================================================================================================================================
Downgrade     1 Package(s)

Total download size: 65 M
Is this ok [y/N]: y
Downloading Packages:
jenkins-2.53-1.1.noarch.rpm                                                                                                                                 |  65 MB     00:08
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : jenkins-2.53-1.1.noarch                                                                                                                                         1/2
  Cleanup    : jenkins-2.54-1.1.noarch                                                                                                                                         2/2
  Verifying  : jenkins-2.53-1.1.noarch                                                                                                                                         1/2
  Verifying  : jenkins-2.54-1.1.noarch                                                                                                                                         2/2

Removed:
  jenkins.noarch 0:2.54-1.1

Installed:
  jenkins.noarch 0:2.53-1.1

진단 단계

• Doing full system backup prior to any update is always recommended, and yum history is NOT meant to replace systems backups.
• General documentation of the system state both prior and after patching is always good practice. This should include running package-cleanup with following flags, --orphans, --problems, --dupes, --leaves.
• yum history undo will require access to all the previous RPM version; thus, need to ensure the older RPM versions are available to the system. It is recommended that prior to doing updates, you closely inspect the output of package-cleanup --orphans to know what currently installed RPMs are no longer available in the enabled repositories. This should not be a concern if using the standard RHEL repositories provided by Red Hat as multiple versions of RPM are maintained in these locations.
• If yum history undo has problem with a given package, it is possible to exclude with the --exclude command line flag, and then can deal with exception manually.
• As after any RPM changes, recommend checking the yum output/logs for any messages and/or rpm{new,orig,save} files created.