<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Patching on IT Admin</title><link>/tags/patching/</link><description>Recent content in Patching on IT Admin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/patching/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing Package Updates Across a Mixed-Distro Fleet with Ansible</title><link>/posts/post-8/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate><guid>/posts/post-8/</guid><description>&lt;p>If your fleet is more than one machine, it&amp;rsquo;s probably more than one distro. Mine is: Ubuntu LTS boxes, Debian, Fedora, and — the interesting one — XCP-ng hypervisors. The goal is simple: one control node, a handful of playbooks, and the ability to answer two questions at any time: &lt;em>what updates are pending?&lt;/em> and &lt;em>are these hosts fully patched?&lt;/em>&lt;/p>
&lt;p>This post builds the whole system from zero. Every file and command is copy-pasteable. The hostnames and IPs below are made up — swap in your own. At the end there&amp;rsquo;s a list of the quirks that actually cost me debugging time, so you can skip my detours.&lt;/p></description></item></channel></rss>