Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1392009

Summary: Hide traceback in engine.log when adding host with running VM
Product: [oVirt] ovirt-engine Reporter: Lucie Leistnerova <lleistne>
Component: Backend.CoreAssignee: Nobody <nobody>
Status: CLOSED DEFERRED QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, lleistne, mperina
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-07 08:58:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log none

Description Lucie Leistnerova 2016-11-04 15:03:30 UTC
Created attachment 1217420 [details]
engine log

Description of problem:
When adding host to engine with running VM an error is showed with tracebacks. Users don't need to see them.
The host and its VM is added to the engine at the end sucessfully so the error seems to be nothing fatal.

Version-Release number of selected component (if applicable):
ovirt-engine-4.1.0-0.0.master.20161101211323.git410903b.el7.centos.noarch

see attached log

Comment 1 Yaniv Kaul 2016-11-06 06:30:14 UTC
Users do not see engine.log.
But the real question is - is the VDSM actually recovering from a crash?

In addition, why would you add a host with a running VM? Of which setup? Is it identified as an external VM?

I'm inclined to close this as a WONTFIX or NOTABUG - doesn't look like a remotely interesting scenario - but perhaps I'm missing some context.

Comment 2 Lucie Leistnerova 2016-11-07 08:14:28 UTC
User in this context is administrator that installed engine and takes care of it. And he can see to logs.

VDSM is not recovering and yes the VM is added as external.

According to BZ 1327848 if I add host to engine and it is already added to other one, no warning is given and it's added without problems. So, when the engine allows it why not hide the traceback.

Comment 3 Yaniv Kaul 2016-11-07 08:58:14 UTC
(In reply to Lucie Leistnerova from comment #2)
> User in this context is administrator that installed engine and takes care
> of it. And he can see to logs.
> 
> VDSM is not recovering and yes the VM is added as external.
> 
> According to BZ 1327848 if I add host to engine and it is already added to
> other one, no warning is given and it's added without problems. So, when the
> engine allows it why not hide the traceback.

Just because it's not worth the effort, not because it cannot be done - there are simply higher priority items to resolve.