<?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[Adding datastores to storage policy does not work properly]]></title><description><![CDATA[<p dir="auto"><strong>Environment</strong></p>
<ul>
<li>MultiPortal Version: 1.1.1</li>
<li>Proxmox VE Version: 8.4.0</li>
<li>Deployment Type: HA Cluster</li>
<li>Browser (if UI issue): Any</li>
</ul>
<p dir="auto"><strong>Description</strong><br />
After adding additional datastore to my storage policies the config does not get applied to all systems.<br />
Moving a VM from to the newly added datastore it creates this error/warning:<br />
torage is being used (local-lvm), while not set in the VDC Storage Policy. VM.</p>
<p dir="auto">Also: Creating a new policy with the new datastore works, but if I add the policy to an existing virtual datacenter the storage is still not recognized. Warning stays the same.</p>
<p dir="auto"><strong>Steps to Reproduce</strong> (if applicable)</p>
<ol>
<li>Open Datacenters</li>
<li>Edit existing datacenter</li>
<li>Add datastore to storage policy or create a new one<br />
3.a: If new policy add the policy to an existing virtual datacenter</li>
<li>move existing vm to the new datastore.</li>
<li>go to the vm in MultiPortal, the error should appear.</li>
</ol>
<p dir="auto"><strong>Expected Behavior</strong><br />
The system recognizes the new datastore being a part of ether an existing policy or of a new policy that has been added to the virtual datastore</p>
<p dir="auto"><strong>Actual Behavior</strong><br />
Ether Way, the datastore is not recognized.</p>
<p dir="auto"><strong>Logs/Screenshots</strong><br />
<img src="/assets/uploads/files/1780589599375-e9c1477b-2416-45f2-88bf-0a55b96553ca-image.jpeg" alt="e9c1477b-2416-45f2-88bf-0a55b96553ca-image.jpeg" class=" img-fluid img-markdown" /><br />
<img src="/assets/uploads/files/1780589615954-4ba41655-b674-4698-9281-99052fc68356-image.jpeg" alt="4ba41655-b674-4698-9281-99052fc68356-image.jpeg" class=" img-fluid img-markdown" /><br />
<img src="/assets/uploads/files/1780589642972-4f520ead-94e8-48d1-9c63-98b64ef66aef-image.jpeg" alt="4f520ead-94e8-48d1-9c63-98b64ef66aef-image.jpeg" class=" img-fluid img-markdown" /></p>
<p dir="auto">(Yes i know local lvm isnt optimal, this is a test)<br />
Regards,<br />
Felix</p>
]]></description><link>https://forum.multiportal.io/topic/25/adding-datastores-to-storage-policy-does-not-work-properly</link><generator>RSS for Node</generator><lastBuildDate>Thu, 18 Jun 2026 06:25:08 GMT</lastBuildDate><atom:link href="https://forum.multiportal.io/topic/25.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 04 Jun 2026 16:14:39 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Adding datastores to storage policy does not work properly on Thu, 04 Jun 2026 23:24:21 GMT]]></title><description><![CDATA[<p dir="auto">Hey <a class="plugin-mentions-user plugin-mentions-a" href="/user/csmo" aria-label="Profile: csmo">@<bdi>csmo</bdi></a></p>
<p dir="auto">I’ve just sent you a message asking for your logs, there is some information that I need to check.</p>
<p dir="auto">The most common issue that comes up, specifically with local-lvm, is if you’re running more than one Proxmox node. Are you able to confirm if you have more than one node, that shares the same name?</p>
<p dir="auto">Matt</p>
]]></description><link>https://forum.multiportal.io/post/69</link><guid isPermaLink="true">https://forum.multiportal.io/post/69</guid><dc:creator><![CDATA[woody]]></dc:creator><pubDate>Thu, 04 Jun 2026 23:24:21 GMT</pubDate></item></channel></rss>