<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[CPU Models inconsistent after adding new nodes to the cluster.]]></title><description><![CDATA[<p dir="auto"><strong>Environment</strong></p>
<ul>
<li>MultiPortal Version:  1.2.1</li>
<li>Proxmox VE Version: 9.2.6</li>
<li>Deployment Type: HA Cluster</li>
</ul>
<p dir="auto"><strong>Description</strong><br />
We have only 1 specific CPU Model enabled at datacenter level. While we add new nodes to our cluster, then the new host have enabled 71 CPU Models on the database. On the WebUI there are likely random things enabled / disabled while we flip through the sites.</p>
<p dir="auto"><strong>Steps to Reproduce</strong> (if applicable)</p>
<ol>
<li>Disable all CPU Models and enable some / one CPU Model(s).</li>
<li>Add new nodes to the cluster.</li>
<li>Some CPU Models you previously disabled becomes randomly enabled.</li>
</ol>
<p dir="auto"><strong>Expected Behavior</strong><br />
New nodes in the cluster get the CPU Models from the existing Nodes.</p>
<p dir="auto"><strong>Actual Behavior</strong><br />
New nodes become 71 default enabled CPU Models</p>
]]></description><link>https://forum.multiportal.io/topic/97/cpu-models-inconsistent-after-adding-new-nodes-to-the-cluster.</link><generator>RSS for Node</generator><lastBuildDate>Sun, 20 Sep 2026 20:20:55 GMT</lastBuildDate><atom:link href="https://forum.multiportal.io/topic/97.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 07 Sep 2026 15:02:36 GMT</pubDate><ttl>60</ttl></channel></rss>