Dear Yedidiah (fantastic name), I personally did not make any changes on the DB, would not try that unless absolutely required. There is no custom vdsm hook added, related to any disk operations. The one and only we have atm is to trigger DSN record updates when VM is destroyed, nothing disk related. You mentioned: "Seems to mean that the engine got from VDSM information about a VM, that includes a disk which is not in the engine's DB." I have another issue reported to oVirt community: "Stuck in 'Finalizing' disk image upload". It could be related. The image physically is not there any more, but there is still ticket which fails to close. Maybe its related. On 18/07/2019, 09:19, "Yedidyah Bar David" <didi@redhat.com> wrote: Hi, On Thu, Jul 18, 2019 at 12:45 AM Vrgotic, Marko <M.Vrgotic@activevideo.com> wrote: > > Dear oVirt, > > > > I was not able to find out meaning behind following WARN message: > > > > WARN [org.ovirt.engine.core.vdsbroker.libvirt.VmDevicesConverter] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [] unmanaged disk with path '/var/run/vdsm/payload/0687ad1a-4827-48d9-8629-b29a000df280.760410382a41ff5e6b1ee9365856517e.img' is ignored > > > > Will somebody be so kind to clarify the actual meaning of it or point me in right direction of cause? > > > > I can provide more information if required. > > > > Kindly awaiting your reply. Changed the subject and added Arik, the author of the patch that introduced this warning: https://gerrit.ovirt.org/70018 Seems to mean that the engine got from VDSM information about a VM, that includes a disk which is not in the engine's DB. Not sure how this could have happened - perhaps you manually changed the DB, or have a vdsm hook that adds it, or there was some problem around the time it was added or removed, or there is some other bug. You might check your logs (both engine and vdsm) around the relevant times for each of above. Best regards, -- Didi