Bug 787936

Summary: debugging output shown on ovirt-node tui
Product: [Retired] oVirt Reporter: Joey Boggs <jboggs>
Component: vdsmAssignee: Joey Boggs <jboggs>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: unspecifiedCC: abaron, acathrow, bazulay, danken, iheim, jboggs, mburns, ovirt-bugs, ovirt-maint, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 787661 Environment:
Last Closed: 2013-01-30 22:50:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 787661    
Bug Blocks:    

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.