Bug 1119566

Summary: Configuring the Netconsole with ipv4 address failed
Product: [Retired] oVirt Reporter: Guangbo Sun <guasun>
Component: ovirt-nodeAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 3.5CC: cshao, fdeutsch, gklein, gouyang, hadong, huiwa, jboggs, leiwang, mgoldboi, ovirt-bugs, rbalakri, rbarry, yaniwang, ycui, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:31:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The error information that shows on the screen none

Description Guangbo Sun 2014-07-15 05:13:37 UTC 
Created attachment 918058 [details]
The error information that shows on the screen

Description of problem:
Configuring the Netconsole with ipv4 address failed.

Version-Release number of selected component (if applicable):
ovirt-node-iso-3.5.0.ovirt35.20140707.el6.iso


How reproducible:
100%
Not regression bug
QA Whiteboard: TUI

Steps to Reproduce:
1. Install ovirt-node-iso-3.5.0.ovirt35.20140707.el6.iso correctly
2. Log in ovirt-node and configure the network
3. Enter Logging page 
4. Configure Netconsole with IPV4 address
5. Click <Save> button

Actual results:
After step 5, the following information shows on the screen:
An error appeared in the UI: NameError("name 'port' is not defined",)
Press ENTER to logout ...
or enter 's' to drop to shell

Expected results:
Configure the Netconsole with ipv4 address successfully

Additional info:
Comment 1 Fabian Deutsch 2014-07-24 16:02:40 UTC 
This is a mass change, moving bugs of merged patches into MODIFIED.

Please correct the state, if you think that the move was not justified.
Comment 3 Sandro Bonazzola 2014-10-17 12:31:28 UTC 
oVirt 3.5 has been released and should include the fix for this issue.