Created attachment 1368007 [details] Same host event 10 times Description of problem: [GUI] - each event in host Events list appears 10 times. Version-Release number of selected component (if applicable): Software Version:4.2.0.2-0.1.el7 How reproducible: 100% Steps to Reproduce: 1. Open the Hosts page and move host to maintenance/activate. 2. Open the Events tab. Actual results: You can see the same line 10 times. Expected results: One line per event Additional info: see attached snapshot
Works for me on latest ovirt master (git 4265064) Was this a fresh install or an upgrade?
Created attachment 1368054 [details] works for me
(In reply to Greg Sheremeta from comment #1) > Works for me on latest ovirt master (git 4265064) > > Was this a fresh install or an upgrade? It was on a fresh installation of latest rhv 4.2.0-11 if you want you can take a look at the engine: https://hosted-engine-02.scl.lab.tlv.redhat.com/ovirt-engine the same issue appears in other qe env: https://jenkins-vm-03.qa.lab.tlv.redhat.com
What happens when querying for host events in the API? Other objects?
>>> events = api.events.list(query='host=host_mixed_1') >>> for e in events: ... print(e.get_description()) ... Status of host host_mixed_1 was set to Up. VDSM host_mixed_1 command HSMGetAllTasksStatusesVDS failed: Recovering from crash or Initializing VDSM host_mixed_1 command SpmStatusVDS failed: Recovering from crash or Initializing Seems fine in the database. It could be a UI problem, or a problem with the query we use.
severity?
(In reply to Yaniv Kaul from comment #6) > severity? It looks bad: medium-high
Alexander, can you take a look?
So I looked into this, and the problem is in the backend. The result set on the backend contains multiple copies of the same row. The UI doesn't do anything but display the data.
Adding host to maintenance shows only one event, other actions also. So it seems ok in my environment. Feel free to reopen if it happens again. verified in ovirt-engine-webadmin-portal-4.2.1.1-0.1.el7.noarch
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 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.