Updating attached VM disk cause many warnings Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
DescriptionMarian Jankular
2020-06-01 09:57:53 UTC
customer is not able to backup vm with SEP Sesam backup as api is returning 'null'
+++ This bug was initially created as a clone of Bug #1820980 +++
Description of problem:
Update attached disk cause many WARNINGS in the engine logs, no apparent effect other than that:
2020-04-04 17:29:41,623+03 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-16) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
Version-Release number of selected component (if applicable):
4.4.0-0.31.master.el8ev
How reproducible:
100%
Steps to Reproduce:
1.Create VM
2.attach a disk
3.checkout engine logs
Actual results:
See the WARN errors.
Expected results:
Additional info:
--- Additional comment from Polina on 2020-04-06 07:48:28 UTC ---
I see the same warnings in engine when sending get disks.
The following sequence of GET requests is sent.
https://{{host}}/ovirt-engine/api/datacentershttps://{{host}}/ovirt-engine/api/datacenters/a2a8201e-bcbe-4bb1-b207-d11a7d84bee6/storagedomainshttps://{{host}}/ovirt-engine/api/datacenters/a2a8201e-bcbe-4bb1-b207-d11a7d84bee6/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/disks
In response to the get disks there is a 'null' in all the links :
...
<actions>
<link href="/ovirt-engine/api/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/null/ca60f727-8821-4b67-8f2e-c8f9f8011354/move" rel="move"/>
<link href="/ovirt-engine/api/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/null/ca60f727-8821-4b67-8f2e-c8f9f8011354/register" rel="register"/>
<link href="/ovirt-engine/api/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/null/ca60f727-8821-4b67-8f2e-c8f9f8011354/copy" rel="copy"/>
<link href="/ovirt-engine/api/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/null/ca60f727-8821-4b67-8f2e-c8f9f8011354/sparsify" rel="sparsify"/>
<link href="/ovirt-engine/api/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/null/ca60f727-8821-4b67-8f2e-c8f9f8011354/export" rel="export"/>
</actions>
<name>OVF_STORE</name>
<description>OVF_STORE</description>
<link href="/ovirt-engine/api/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/null/ca60f727-8821-4b67-8f2e-c8f9f8011354/permissions" rel="permissions"/>
<link href="/ovirt-engine/api/storagedomains/99db88f3-a794-491c-9cdc-0925289aab70/null/ca60f727-8821-4b67-8f2e-c8f9f8011354/statistics" rel="statistics"/>
....
attached logs.tar.gz contains full response with 'null' in all links
--- Additional comment from Polina on 2020-04-06 07:49:17 UTC ---
--- Additional comment from Tal Nisan on 2020-04-20 08:18:10 UTC ---
Should be solved in imageio 2.0, please retest
--- Additional comment from Shir Fishbain on 2020-04-20 12:37:45 UTC ---
Verified - The warnings don't appear in the engine log when updating the attached VM disk.
ovirt-engine-4.4.0-0.33.master.el8ev.noarch
vdsm-4.40.13-1.el8ev.x86_64
--- Additional comment from Sandro Bonazzola on 2020-05-20 19:57:49 UTC ---
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.
Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.
Hi Marian,
This was fixed in 4.4, however I see that you cloned it saying it was reproduced in 4.4.0, can you please confirm that you still have the issue on 4.4.0?
Verified - The warnings don't appear in the engine log when updating the attached VM disk.
ovirt-engine-4.3.11.2-0.1.el7.noarch
vdsm-4.30.50-1.el7ev.x86_64
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 (Red Hat Virtualization Engine security, bug fix 4.3.11), 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/RHBA-2020:4112