Bug 1320902 - TUI crashed when configured Rsyslog Server Port in "Logging page".
Summary: TUI crashed when configured Rsyslog Server Port in "Logging page".
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: Huijuan Zhao
URL:
Whiteboard:
Depends On:
Blocks: 1354597
TreeView+ depends on / blocked
 
Reported: 2016-03-24 09:43 UTC by Zhenlin Zhong
Modified: 2016-09-11 13:04 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-21 18:02:26 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
/var/log/*.* (6.37 MB, application/x-gzip)
2016-03-24 09:43 UTC, Zhenlin Zhong 		no flags Details
View All

Description Zhenlin Zhong 2016-03-24 09:43:04 UTC 
Created attachment 1139879 [details]
/var/log/*.*

Description of problem:
TUI crashed when configured Rsyslog Server Port in "Logging page".

Version-Release number of selected component (if applicable):
rhevh-7.2-20160322.1.el7ev
ovirt-node-3.6.1-8.0

How reproducible:
100%

Steps to Reproduce:
1.Install RHEV-H 7.2 on local machine via pxe.
2.Configure network by dhcp.
3.Enter Logging page,configure "RSyslog Server Port" as 534.
4.Click "save".
5.Login in rhevh again,Reconfigure "Logrotate Server Port" as 7777.
6.Click "save".

Actual results:
1.After step 4,the TUI crashed and return "Login" page.
2.After step 6,it always stay in "checking pre-conditions" page unless restart the rhevh.

Expected results:
No error for the logging configuration.

Additional info:
Comment 1 Fabian Deutsch 2016-04-12 12:24:27 UTC 
We should get rid of the crash.
Comment 2 Yaniv Kaul 2016-05-04 18:13:15 UTC 
Any plans to do it in 3.6.6? Otherwise, please defer.
Comment 5 Fabian Deutsch 2016-07-21 18:02:26 UTC 
In RHEV 4.0 we'll be using Cockpit for administration.
Note You need to log in before you can comment on or make changes to this bug.