Bug 1854478 - [UI] Inject copy host network failure into the event log UI.
Summary: [UI] Inject copy host network failure into the event log UI.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.4.1.7
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ovirt-4.4.2
: 4.4.2.1
Assignee: eraviv
QA Contact: michal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-07 14:22 UTC by michal
Modified: 2020-09-18 07:12 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.4.2.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-18 07:12:43 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.4+
mtessun: planning_ack+
dholler: devel_ack+
mburman: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 110204 0 master MERGED core: copy host networks - audit iface count mismatch 2020-08-21 09:34:43 UTC

Description michal 2020-07-07 14:22:53 UTC 
Description of problem:

when copy host network fails, there are missing event log UI.

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


How reproducible:


Steps to Reproduce:
1.Create network on Cluster 
2.Attach network to nic at Host that have some nics
3.Copy host network-choose Host that have less nics, from host in step 2

Actual results:
copy host network fails.
The error message appears in engine.log:

ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-79) [] Operation Failed: [Cannot copy networks to Host. Interface count of destination host has to be at least as high as that of the source host.]
Expected results:
Error message should appear in events log UI

Additional info:
Comment 1 michal 2020-08-10 07:12:42 UTC 
verified on - rhvm-4.4.2.1-0.15.el8ev.noarch
Comment 2 Sandro Bonazzola 2020-09-18 07:12:43 UTC 
This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020.

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