Red Hat Bugzilla – Bug 1525596
[REST] entrypoint for events returns Blank template element without href nor id
Last modified: 2018-05-15 13:48:01 EDT
Description of problem: When accessing the events entrypoint (ovirt-engine/api/events), if one of the events is related to the Blank template, this element is returned with no href nor id. Version-Release number of selected component (if applicable): ovirt-engine-4.2.0-0.6.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Access events entrypoint @ovirt-engine/api/events 2. Search for Blank template element 3. Check that nor href nor id is present in the element Actual results: <event href="..." id="..."> ... <template> <name>Blank</name> </template> ... </event> Expected results: <event href="..." id="..."> ... <template href="/ovirt-engine/api/templates/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <name>Blank</name> </template> ... </event> Additional info: This is only occurring with the Blank template all other template elements are returned correctly
Ori, can you take a look at this? And maybe assign to yourself? I think that the problem is that the id of the blank template is all zeros, and we assume that that means that there is no template.
severity?
Can you please provide an example of a flow, that will result in an event that relates to the blank template?
(In reply to Ori Liel from comment #3) > Can you please provide an example of a flow, that will result in an event > that relates to the blank template? Same workflow as in original description with VM creation from Blank template.
Verified that events related to Blank template have <template> element with both, href and id. Version RHV 4.2.2
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Tag 'ovirt-engine-4.2.2.4' doesn't contain patch 'https://gerrit.ovirt.org/87561'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.2.2.4 For more info please contact: rhv-devops@redhat.com
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, 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/RHEA-2018:1488