how to downgrade rhel 7.3 to 7.2
I did not know when I do yum update, my rhel is updgraded from 7.2 to 7.3. When I try to install Cloudera Data Science Workbench, it said rhel 7.3 is not comparable. Is there a way to downgrade it from 7.3 to 7.2?
Responses
You can roll back to 7.2 by using yum history to rollback to the update before the one that moved you to 7.3.
# yum history list (to see which update moved you to 7.3)
# yum history rollback <#> ('#' is the transaction number from the history list)
If you want to stay at 7.2, and you are getting patches directly from Red Hat you could then update but ensure that your packages stay on 7.2 versions:
# yum update --releasever=7.2
Be careful with "rollback" as this would cancel all yum transactions up to that point. Hence, you could safely use "yum history undo #" (# yum transaction ID number) to revert any particular yum transactions. Check out the yum man page for more details...
The undo/redo commands act on the specified transaction, undo’ing or repeating the work of that transaction. While the rollback command will undo all transactions up to the point of the specified transaction. For example, if you have 3 transactions, where package A; B and C where installed respectively. Then "undo 1" will try to remove package A, "redo 1" will try to install package A (if it is not still installed), and "rollback 1" will try to remove packages B and C. Note that after a "rollback 1" you will have a fourth transaction, although the ending rpmdb version (see: yum version) should be the same in transactions 1 and 4.
That's a valid point as well. However, depending on the number of transactions that have occurred after the 7.3 update some of those transactions might depend on some of the packages that are about to be "undone" anyhow. Also, if the goal is to truly remain on 7.2, in this case, it might be wise to go ahead and roll it all back (if feasible) and then reapply each one using the 'releasever' option to yum. In this way all of your installed packages will have come only from the 7.2 patch set.
Well, setting release version using above method is not persistent, you would need to use 'subscription manager' to get this done persistently. Check this article https://access.redhat.com/solutions/238533
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.