Bug 784331

Summary: [ovirt] [engine-core] logging: add proper logging in case engine decides not to reconstruct
Product: [Retired] oVirt Reporter: Haim <hateya>
Component: ovirt-engine-coreAssignee: lpeer <lpeer>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, amureini, iheim, mgoldboi, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-12 07:36:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
rhevm log. none

Description Haim 2012-01-24 15:33:42 UTC
Created attachment 557256 [details]
rhevm log.

Description of problem:

there are several flows where engine-core should but decides not to reconstruct domain, I would like to get a proper log message stating that reconstruct flow will not enter due to $reason.

in that case, I see the following entry: 

2012-01-24 17:29:47,696 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.MarkPoolInReconstructModeVDSCommand] (QuartzScheduler_Worker-23) START, MarkPoolInReconstructModeVDSCommand(storagePoolId = c95cd29b-8ba9-490b-b544-956c787bb955, i
gnoreFailoverLimit = false, compatabilityVersion = null, reconstructMarkAction = ClearCache), log id: 4d899b3b

but engine doesn't enter the reconstruct flow - and I don't know way.

Comment 1 Itamar Heim 2012-12-12 07:36:01 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.