Bug 1119566 - Configuring the Netconsole with ipv4 address failed
Summary: Configuring the Netconsole with ipv4 address failed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.5
Hardware: Unspecified
OS: Linux
high
medium
Target Milestone: ---
: 3.5.0
Assignee: Ryan Barry
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-15 05:13 UTC by Guangbo Sun
Modified: 2016-02-10 19:40 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-17 12:31:28 UTC
oVirt Team: Node


Attachments (Terms of Use)
The error information that shows on the screen (7.30 KB, image/png)
2014-07-15 05:13 UTC, Guangbo Sun
no flags Details


Links
System ID Priority Status Summary Last Updated
oVirt gerrit 30118 master MERGED Unbreak netconsole Never

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.


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