<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>how to revert os patching on centos 8 Archives - Linux Windows and android Tutorials</title>
	<atom:link href="https://www.osradar.com/tag/how-to-revert-os-patching-on-centos-8/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.osradar.com</link>
	<description>tutorials and news and Seurity</description>
	<lastBuildDate>Thu, 26 Dec 2019 23:24:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.8.13</generator>
	<item>
		<title>How To Revert OS Patching on CentOS 8 / RHEL 8</title>
		<link>https://www.osradar.com/how-to-revert-os-patching-on-centos-8-rhel-8/</link>
					<comments>https://www.osradar.com/how-to-revert-os-patching-on-centos-8-rhel-8/#respond</comments>
		
		<dc:creator><![CDATA[sabi]]></dc:creator>
		<pubDate>Fri, 27 Dec 2019 11:01:00 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Centos 8]]></category>
		<category><![CDATA[how to revert os patching on centos 8]]></category>
		<category><![CDATA[revert os pathcing]]></category>
		<category><![CDATA[revert patching on linux]]></category>
		<guid isPermaLink="false">https://www.osradar.com/?p=17075</guid>

					<description><![CDATA[<p>Sometimes we run updates on our system and they may break your system or application that is running on top of it. Although these occurs rarely but we will see here that how we can revert our updates. Follow the below steps to proceed towards reverting. Step 1: Update History You can see the history [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.osradar.com/how-to-revert-os-patching-on-centos-8-rhel-8/">How To Revert OS Patching on CentOS 8 / RHEL 8</a> appeared first on <a rel="nofollow" href="https://www.osradar.com">Linux  Windows and android  Tutorials</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Sometimes we run updates on our system and they may break your system or application that  is running on top of it. Although these occurs rarely but we will see here that how we can revert our updates. Follow the below steps to proceed towards reverting.</p>



<h3><strong>Step 1: Update History</strong></h3>



<p>You can see the history of updating all activities you have made so for with yum command including the OS Patching by running. Run with sudo.</p>



<pre class="wp-block-verse">[root@localhost sabi]# yum history<br> ID     | Command line             | Date and time    | Action(s)      | Altered<br> <code>16 | install -y redis         | 2019-12-24 06:28 | Install        |    1    15 | -y install @mariadb      | 2019-12-24 06:22 | Install        |   10    14 | install -y nodejs nginx  | 2019-12-24 06:21 | Install        |    9  &lt; 13 | install -y epel-release  | 2019-12-24 06:20 | Install        |    7 &gt;  12 | -y update                | 2019-12-24 05:24 | I, U           |   92 EE 11 | install -y VirtualBox-6. | 2019-12-24 05:00 | Install        |   35 EE 10 | -y install wget          | 2019-12-24 04:23 | Upgrade        |    1     9 | install -y kernel-devel  | 2019-12-23 21:05 | Install        |  123     8 | -y update                | 2019-12-23 19:24 | I, U           |   78 EE</code></pre>



<p>As you can see the output above, you can see the ID of updates. </p>



<p>You can also find more information of the history by typing</p>



<pre class="wp-block-verse">yum history info &lt;ID&gt;</pre>



<p><strong>Output:</strong></p>



<pre class="wp-block-verse">[root@localhost sabi]# yum history info 8<br> Transaction ID : 8<br> Begin time     : Mon 23 Dec 2019 07:24:42 PM PKT<br> Begin rpmdb    : 1325:302c06910b5035a294f72fe71b9b0411003a5791<br> End time       : Mon 23 Dec 2019 07:30:53 PM PKT (6 minutes)<br> End rpmdb      : 1329:2256499a1b7cbafa860a3d6291d1c09aeeca3b53<br> User           : Sabir Hussain <br> Return-Code    : Success<br> Releasever     : 8<br> Command Line   : -y update<br> Packages Altered:<br>     Install  grub2-tools-efi-1:2.02-66.el8_0.1.x86_64               @BaseOS<br>     Install  kernel-4.18.0-80.11.2.el8_0.x86_64                     @BaseOS<br>     Install  kernel-core-4.18.0-80.11.2.el8_0.x86_64                @BaseOS<br>     Install  kernel-modules-4.18.0-80.11.2.el8_0.x86_64             @BaseOS<br>     Upgrade  bash-4.4.19-8.el8_0.x86_64                             @BaseOS<br>     Upgraded bash-4.4.19-7.el8.x86_64                               @@System<br>     Upgrade  bind-export-libs-32:9.11.4-17.P2.el8_0.1.x86_64        @BaseOS<br>     Upgraded bind-export-libs-32:9.11.4-16.P2.el8.x86_64            @@System<br>     Upgrade  bpftool-4.18.0-80.11.2.el8_0.x86_64                    @BaseOS<br>     Upgraded bpftool-4.18.0-80.el8.x86_64                           @@System<br>     Upgrade  cockpit-185.1-1.el8_0.x86_64                           @BaseOS<br>     Upgraded cockpit-185-2.el8.x86_64                               @@System<br>     Upgrade  cockpit-bridge-185.1-1.el8_0.x86_64                    @BaseOS<br>     Upgraded cockpit-bridge-185-2.el8.x86_64                        @@System<br>     Upgrade  cockpit-system-185.1-1.el8_0.noarch                    @BaseOS<br>     Upgraded cockpit-system-185-2.el8.noarch                        @@System<br>     Upgrade  cockpit-ws-185.1-1.el8_0.x86_64                        @BaseOS<br>     Upgraded cockpit-ws-185-2.el8.x86_64                            @@System<br>     Upgrade  device-mapper-multipath-0.7.8-7.el8_0.2.x86_64         @BaseOS<br>     Upgraded device-mapper-multipath-0.7.8-7.el8.x86_64             @@System<br>     Upgrade  device-mapper-multipath-libs-0.7.8-7.el8_0.2.x86_64    @BaseOS<br>     Upgraded device-mapper-multipath-libs-0.7.8-7.el8.x86_64        @@System<br>     Upgrade  dracut-049-10.git20190115.el8_0.1.x86_64               @BaseOS<br>     Upgraded dracut-049-10.git20190115.el8.x86_64                   @@System<br>     Upgrade  dracut-config-rescue-049-10.git20190115.el8_0.1.x86_64 @BaseOS<br>     Upgraded dracut-config-rescue-049-10.git20190115.el8.x86_64     @@System<br>     Upgrade  dracut-network-049-10.git20190115.el8_0.1.x86_64       @BaseOS<br>     Upgraded dracut-network-049-10.git20190115.el8.x86_64           @@System<br>     Upgrade  dracut-squash-049-10.git20190115.el8_0.1.x86_64        @BaseOS<br>     Upgraded dracut-squash-049-10.git20190115.el8.x86_64            @@System<br>     Upgrade  grub2-common-1:2.02-66.el8_0.1.noarch                  @BaseOS<br>     Upgraded grub2-common-1:2.02-66.el8.noarch                      @@System<br>     Upgrade  grub2-pc-1:2.02-66.el8_0.1.x86_64                      @BaseOS</pre>



<p>Similarly you can see the information about other ID&#8217;s. </p>



<h3><strong>Step 2: Revert Updates</strong></h3>



<p>After identifying the OS patching ID and Kernel updates ID (mostly updated kernel is installed along with OS patching), move forward to revert updates one by one.</p>



<h3><strong>Step 3: Kernel </strong></h3>



<p>This step will not be applicable if the Kernel was installed along with OS patching (yum update).</p>



<p>Type the following command to revert the history followed by ID. Press <strong>Y</strong> to Continue.</p>



<pre class="wp-block-verse">yum history undo &lt;ID&gt;</pre>



<p><strong>Output:</strong></p>



<pre class="wp-block-verse">[root@localhost sabi]# yum history undo 8<br> Last metadata expiration check: 0:01:19 ago on Wed 25 Dec 2019 12:47:38 PM PKT.<br> Undoing transaction 8, from Mon 23 Dec 2019 07:24:42 PM PKT<br>     Install  grub2-tools-efi-1:2.02-66.el8_0.1.x86_64               @BaseOS<br>     Install  kernel-4.18.0-80.11.2.el8_0.x86_64                     @BaseOS<br>     Install  kernel-core-4.18.0-80.11.2.el8_0.x86_64                @BaseOS<br>     Install  kernel-modules-4.18.0-80.11.2.el8_0.x86_64             @BaseOS<br>     Upgrade  bash-4.4.19-8.el8_0.x86_64                             @BaseOS<br>     Upgraded bash-4.4.19-7.el8.x86_64                               @@System<br>     Upgrade  bind-export-libs-32:9.11.4-17.P2.el8_0.1.x86_64        @BaseOS<br>     Upgraded bind-export-libs-32:9.11.4-16.P2.el8.x86_64            @@System<br>     Upgrade  bpftool-4.18.0-80.11.2.el8_0.x86_64                    @BaseOS<br>     Upgraded bpftool-4.18.0-80.el8.x86_64                           @@System<br>     Upgrade  cockpit-185.1-1.el8_0.x86_64                           @BaseOS<br>     Upgraded cockpit-185-2.el8.x86_64                               @@System<br>     Upgrade  cockpit-bridge-185.1-1.el8_0.x86_64                    @BaseOS<br>     Upgraded cockpit-bridge-185-2.el8.x86_64                        @@System<br>     Upgrade  cockpit-system-185.1-1.el8_0.noarch                    @BaseOS<br>     Upgraded cockpit-system-185-2.el8.noarch                        @@System<br>     Upgrade  cockpit-ws-185.1-1.el8_0.x86_64                        @BaseOS<br>     Upgraded cockpit-ws-185-2.el8.x86_64                            @@System<br>     Upgrade  device-mapper-multipath-0.7.8-7.el8_0.2.x86_64         @BaseOS<br>     Upgraded device-mapper-multipath-0.7.8-7.el8.x86_64             @@System<br>     Upgrade  device-mapper-multipath-libs-0.7.8-7.el8_0.2.x86_64    @BaseOS<br>     Upgraded device-mapper-multipath-libs-0.7.8-7.el8.x86_64        @@System<br>     Upgrade  dracut-049-10.git20190115.el8_0.1.x86_64               @BaseOS<br>     Upgraded dracut-049-10.git20190115.el8.x86_64                   @@System<br>     Upgrade  dracut-config-rescue-049-10.git20190115.el8_0.1.x86_64 @BaseOS<br>     Upgraded dracut-config-rescue-049-10.git20190115.el8.x86_64     @@System<br>     Upgrade  dracut-network-049-10.git20190115.el8_0.1.x86_64       @BaseOS<br>     Upgraded dracut-network-049-10.git20190115.el8.x86_64           @@System<br>     Upgrade  dracut-squash-049-10.git20190115.el8_0.1.x86_64        @BaseOS<br>     Upgraded dracut-squash-049-10.git20190115.el8.x86_64            @@System<br>     Upgrade  grub2-common-1:2.02-66.el8_0.1.noarch                  @BaseOS<br>     Upgraded grub2-common-1:2.02-66.el8.noarch                      @@System<br>     Upgrade  grub2-pc-1:2.02-66.el8_0.1.x86_64                      @BaseOS<br>     Upgraded grub2-pc-1:2.02-66.el8.x86_64                          @@System<br>     Upgrade  grub2-pc-modules-1:2.02-66.el8_0.1.noarch              @BaseOS</pre>



<h3><strong>Step 4: Revert Packages</strong></h3>



<p>Run the<strong> yum history undo with ID</strong> to revert the activities (revert OS updates)</p>



<pre class="wp-block-verse">[root@localhost sabi]# yum history undo 6<br> Last metadata expiration check: 0:04:21 ago on Wed 25 Dec 2019 12:47:38 PM PKT.<br> Undoing transaction 6, from Sun 22 Dec 2019 02:17:13 PM PKT<br>     Install ipvsadm-1.29-8.el8.x86_64 @AppStream<br> Dependencies resolved.<br>  Package          Arch            Version             Repository           Size<br> Removing:<br>  ipvsadm          x86_64          1.29-8.el8          @AppStream           83 k<br> Transaction Summary<br> Remove  1 Package<br> Freed space: 83 k<br> Is this ok [y/N]: y<br> Running transaction check<br> Transaction check succeeded.<br> Running transaction test<br> Transaction test succeeded.<br> Running transaction<br>   Preparing        :                                                        1/1 <br>   Running scriptlet: ipvsadm-1.29-8.el8.x86_64                              1/1 <br>   Erasing          : ipvsadm-1.29-8.el8.x86_64                              1/1 <br>   Running scriptlet: ipvsadm-1.29-8.el8.x86_64                              1/1 <br>   Verifying        : ipvsadm-1.29-8.el8.x86_64                              1/1 <br> Removed:<br>   ipvsadm-1.29-8.el8.x86_64                                                     <br> Complete!</pre>



<p>After it, reboot system by </p>



<pre class="wp-block-verse">reboot</pre>



<h3><strong>Step 5: Verifying Revert Process</strong></h3>



<p><strong>Kernel</strong></p>



<p>Type the given command to verify the revert process of kernel</p>



<pre class="wp-block-verse">uname -a</pre>



<p><strong>Output:</strong></p>



<pre class="wp-block-verse">[root@localhost sabi]# uname -a<br> Linux localhost.localdomain 4.18.0-80.11.2.el8_0.x86_64 #1 SMP Tue Sep 24 11:32:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux</pre>



<p><strong>Packages</strong></p>



<p>Run the below command to verify the revert process of Packages by comparing new and downgraded version.</p>



<pre class="wp-block-verse">rpm -qa &lt;package name&gt;</pre>



<p>So, that is it. Please share our posts and join <a href="https://t.me/osradar" target="_blank" rel="noreferrer noopener" aria-label="our Telegram Channel (opens in a new tab)">our Telegram Channel</a></p>
<p>The post <a rel="nofollow" href="https://www.osradar.com/how-to-revert-os-patching-on-centos-8-rhel-8/">How To Revert OS Patching on CentOS 8 / RHEL 8</a> appeared first on <a rel="nofollow" href="https://www.osradar.com">Linux  Windows and android  Tutorials</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.osradar.com/how-to-revert-os-patching-on-centos-8-rhel-8/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
