Bug 1720994 - sync all cluster networks - all sync host events are numbered '1/1' in events tab\engine.log
Summary: sync all cluster networks - all sync host events are numbered '1/1' in events...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.3.5
Hardware: All
OS: All
low
low
Target Milestone: ovirt-4.3.6
: 4.3.6.1
Assignee: eraviv
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-17 05:23 UTC by eraviv
Modified: 2019-09-26 19:43 UTC (History)
1 user (show)

Fixed In Version: ovirt-engine-4.3.6.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-26 19:43:04 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.3+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 100859 0 master MERGED engine: enumerate cluster-wide sync-host events 2019-06-26 07:33:38 UTC
oVirt gerrit 101434 0 ovirt-engine-4.3 MERGED engine: enumerate cluster-wide sync-host events 2019-08-06 09:41:37 UTC

Description eraviv 2019-06-17 05:23:49 UTC
Description of problem:

When several hosts are being synced by the operation 'sync all cluster networks' each host sync operation logs a start and end event to the events tab and engine.log. All events are numbered as 1/1



Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create two hosts with out of sync networks
2. Clusters > [your cluster] > logical networks > sync cluster networks
3. inspect event tab - all related events numbered as 1/1

Actual results:
All events are numbered as 1/1

Expected results:
Since this is a multi-host operation the events should be numbered as 'i/N' where i is a running counter and N is the number of hosts being synced.


Additional info:

Comment 1 Michael Burman 2019-08-11 07:19:21 UTC
Verified on - 4.3.6.1-0.1.el7

Comment 2 Sandro Bonazzola 2019-09-26 19:43:04 UTC
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 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.


Note You need to log in before you can comment on or make changes to this bug.