Bug 1854478

Summary: [UI] Inject copy host network failure into the event log UI.
Product: [oVirt] ovirt-engine Reporter: michal <mgold>
Component: BLL.NetworkAssignee: eraviv
Status: CLOSED CURRENTRELEASE QA Contact: michal <mgold>
Severity: low Docs Contact:
Priority: medium    
Version: 4.4.1.7CC: bugs, dholler, mburman, mtessun
Target Milestone: ovirt-4.4.2Flags: pm-rhel: ovirt-4.4+
mtessun: planning_ack+
dholler: devel_ack+
mburman: testing_ack+
Target Release: 4.4.2.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-18 07:12:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.