Bug 1776806

Summary: Cannot read property 'N' of null
Product: [oVirt] ovirt-engine Reporter: jiaohaolin <jiaohaolin>
Component: GeneralAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.7.2CC: amusil, bugs, dholler
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-03 16:52:22 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:
Attachments:
Description Flags
error image none

Description jiaohaolin 2019-11-26 12:22:57 UTC
Created attachment 1639782 [details]
error image

after adding a new network,when I set host network,it will raise a exception that not catched,

Comment 1 Dominik Holler 2019-11-26 13:55:11 UTC
Thanks for reporting the bug.
What is the version of ovirt-engine with this problem?
(e.g. output of sudo rpm -qa ovirt-engine)

Comment 2 RHEL Program Management 2019-11-26 13:55:19 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 3 jiaohaolin 2019-11-27 01:18:21 UTC
the version of ovirt-engine is ovirt-engine-4.3.7.2-1.el7.noarch.And I install the hosts by using ovirt-node-ng-installer-4.3.7-2019112110.el7.iso

Comment 4 Michael Burman 2019-11-27 05:12:35 UTC
HI, 
QE cannot reproduce.
What are the exact steps to reproduce this report?
Is it 100% reproducible? 
Can you provide some more info, what is the network type, is it VM net, non-VM, vlan tagged?

Comment 5 Ales Musil 2019-11-28 06:10:17 UTC
Hi,

can you please attach relevant part from ui.log and engine.log?

Thank you.

Comment 6 Dominik Holler 2019-12-03 16:52:22 UTC
jiaohaolin, please let me know if you not agree.

*** This bug has been marked as a duplicate of bug 1663615 ***