Description of problem: Add-Disk operation failed to complete. - was thrown in rhev-m after refresh of ocp virtualization cluster ( I was adding new vm and template inside ocp to start tests ) Version-Release number of selected component (if applicable): 4.4.1.5-0.17.el8ev How reproducible: 100 Steps to Reproduce: 1. add new provider of ocp virtualization to rhevm 2. create new vm/ template inside ocp 3. check refresh of vm/templates inside rhevm - you will error message Actual results: I got error message inside rhevm about disk Expected results: information should be obtained without errors Additional info: will attach log in comment
Created attachment 1700475 [details] engine.log
possibly related to Benny's I329c4d7d2fc7322e4165acaaa678c5b553c15e01
Possibly related to BZ#1854488
(In reply to Michal Skrivanek from comment #2) > possibly related to Benny's I329c4d7d2fc7322e4165acaaa678c5b553c15e01 Could be, though it seems like it has the same flow as regular disk image so it "should" work. But I don't see the creation itself, nor vdsm logs. Is talayan-pytest-8gw99-worker-rgnr5 a vdsm host? Pavol, can you provide the full logs?
No it is not - talayan-pytest-8gw99-worker-rgnr5 is OCP worker talayan-pytest-8gw99-worker-rgnr5 From my point this is duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1845396 <- process was same for both bugs - to create OCP VM in RHV - now there is code to block creation of diskless ocp vm, so I stop seeing this errorRHV
After discussing this, the callback was not supposed to run for CNV disks (and there was code to prevent it), but it did even before my patch because the disk type was overridden. I posted a fix to avoid running some of the code that is relevant only for regular images so no callback is run, it should also shave a few seconds off the operation
Software Version:4.4.2.2-0.3.el8ev Aug 26, 2020, 7:25:11 PM The disk 'example-disk-claim' was successfully added. No errors on ocp pvcs
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Virtualization security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3807
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days