Bug 787936 - debugging output shown on ovirt-node tui
Summary: debugging output shown on ovirt-node tui
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Joey Boggs
QA Contact:
URL:
Whiteboard: infra
Depends On: 787661
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-07 04:54 UTC by Joey Boggs
Modified: 2016-04-27 00:10 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 787661
Environment:
Last Closed: 2013-01-30 22:50:31 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Joey Boggs 2012-02-07 04:54:43 UTC
+++ This bug was initially created as a clone of Bug #787661 +++

Description of problem:
When configuring storage during the install process, debugging output is printed to the screen.  It should be hidden in the log file

Similar and probably related problem: 
When registering to ovirt-engine, certificate validation also generated similar messages.  

Version-Release number of selected component (if applicable):
2.2.2-2

How reproducible:
always

Steps to Reproduce:
1.start install flow
2.choose disks
3.set password
  
Actual results:
status bar screen shows debug output

Expected results:
Output should go into log, not shown on screen.

Additional info:

--- Additional comment from mburns on 2012-02-06 08:03:55 EST ---

If this issue turns out to be separate issues for the engine and installation, please clone the engine piece to vdsm

--- Additional comment from jboggs on 2012-02-06 23:53:38 EST ---

http://gerrit.ovirt.org/1697  vdsm will be cloned out

Comment 1 Dan Kenigsberg 2012-03-11 16:26:06 UTC
Would you please be more specific, explaining what is the registration-related problem, which vdsm version is affected, and suggested fix?

Comment 2 Itamar Heim 2013-01-30 22:50:31 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


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