Tornedo.tetrain.com Upgrade Plan - Revision history

https://wiki.tetrain.com/index.php?action=history&feed=atom&title=Tornedo.tetrain.com_Upgrade_Plan Tornedo.tetrain.com Upgrade Plan - Revision history 2026-07-25T18:57:29Z Revision history for this page on the wiki MediaWiki 1.43.9 https://wiki.tetrain.com/index.php?title=Tornedo.tetrain.com_Upgrade_Plan&diff=4213&oldid=prev Admin: Fix heading quote characters breaking TOC collapse 2026-07-25T16:43:02Z

<p>Fix heading quote characters breaking TOC collapse</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 16:43, 25 July 2026</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l32">Line 32:</td> <td colspan="2" class="diff-lineno">Line 32:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Current state: '''CentOS Linux 7''' (kernel 3.10.0-1127, fully EOL), 1.8G RAM, 60G disk at 94% used (4.0G free), 126 packages pending. It's the only host in the 19-server scan with these signatures — treat it as a possible single point of failure for authentication until proven otherwise (Step 0 below).</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Current state: '''CentOS Linux 7''' (kernel 3.10.0-1127, fully EOL), 1.8G RAM, 60G disk at 94% used (4.0G free), 126 packages pending. It's the only host in the 19-server scan with these signatures — treat it as a possible single point of failure for authentication until proven otherwise (Step 0 below).</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>== 2. Precision note on <del style="font-weight: bold; text-decoration: none;">"</del>in-place to CentOS Stream 10<del style="font-weight: bold; text-decoration: none;">" </del>— read this before scheduling ==</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>== 2. Precision note on <ins style="font-weight: bold; text-decoration: none;">'</ins>in-place to CentOS Stream 10<ins style="font-weight: bold; text-decoration: none;">' </ins>— read this before scheduling ==</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>There is '''no single-hop tool path from CentOS Linux 7 straight to CentOS Stream 10.''' <code><nowiki>leapp</nowiki></code> (the only real in-place conversion mechanism for this OS family) only supports one major version at a time, and each hop requires its own compatible leapp release/actors. To reach Stream 10 in place, this is actually '''three chained conversions''', each a separate maintenance event with its own reboot and validation pass:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>There is '''no single-hop tool path from CentOS Linux 7 straight to CentOS Stream 10.''' <code><nowiki>leapp</nowiki></code> (the only real in-place conversion mechanism for this OS family) only supports one major version at a time, and each hop requires its own compatible leapp release/actors. To reach Stream 10 in place, this is actually '''three chained conversions''', each a separate maintenance event with its own reboot and validation pass:</div></td></tr> <tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l87">Line 87:</td> <td colspan="2" class="diff-lineno">Line 87:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''RESOLVED.''' Hostname corrected to <code><nowiki>tornedo.tetrain.com</nowiki></code> and locked against cloud-init reset (<code><nowiki>preserve_hostname: true</nowiki></code>). All three certs resubmitted and confirmed: <code><nowiki>status: MONITORING</nowiki></code>, no <code><nowiki>ca-error</nowiki></code>, new expiry '''2028-07-23''' on all three. This item is closed — no further action needed here.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''RESOLVED.''' Hostname corrected to <code><nowiki>tornedo.tetrain.com</nowiki></code> and locked against cloud-init reset (<code><nowiki>preserve_hostname: true</nowiki></code>). All three certs resubmitted and confirmed: <code><nowiki>status: MONITORING</nowiki></code>, no <code><nowiki>ca-error</nowiki></code>, new expiry '''2028-07-23''' on all three. This item is closed — no further action needed here.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>== 3.2 Downtime reality check for <del style="font-weight: bold; text-decoration: none;">"</del>in-place, no downtime<del style="font-weight: bold; text-decoration: none;">" </del>==</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>== 3.2 Downtime reality check for <ins style="font-weight: bold; text-decoration: none;">'</ins>in-place, no downtime<ins style="font-weight: bold; text-decoration: none;">' </ins>==</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Important correction before proceeding: '''a true zero-downtime in-place upgrade is not possible for this server.''' <code><nowiki>leapp</nowiki></code> works by rebooting the machine into a dedicated upgrade environment, performing the OS transformation, then rebooting again into the new major version. <code><nowiki>dirsrv</nowiki></code>/<code><nowiki>krb5kdc</nowiki></code>/<code><nowiki>pki-tomcatd</nowiki></code>/<code><nowiki>httpd</nowiki></code> are unavailable for the duration of each hop's reboot cycle — that's inherent to how leapp works, not a configuration choice. Zero-downtime was only achievable via the replica-and-promote strategy (Section 1's original recommendation), which was set aside in favor of in-place per prior direction.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Important correction before proceeding: '''a true zero-downtime in-place upgrade is not possible for this server.''' <code><nowiki>leapp</nowiki></code> works by rebooting the machine into a dedicated upgrade environment, performing the OS transformation, then rebooting again into the new major version. <code><nowiki>dirsrv</nowiki></code>/<code><nowiki>krb5kdc</nowiki></code>/<code><nowiki>pki-tomcatd</nowiki></code>/<code><nowiki>httpd</nowiki></code> are unavailable for the duration of each hop's reboot cycle — that's inherent to how leapp works, not a configuration choice. Zero-downtime was only achievable via the replica-and-promote strategy (Section 1's original recommendation), which was set aside in favor of in-place per prior direction.</div></td></tr> </table>

Admin https://wiki.tetrain.com/index.php?title=Tornedo.tetrain.com_Upgrade_Plan&diff=4210&oldid=prev Admin: Publish upgrade plan documentation 2026-07-25T16:41:29Z

<p>Publish upgrade plan documentation</p> <a href="https://wiki.tetrain.com/index.php?title=Tornedo.tetrain.com_Upgrade_Plan&diff=4210">Show changes</a>

Admin