Bug 784331 - [ovirt] [engine-core] logging: add proper logging in case engine decides not to reconstruct
Summary: [ovirt] [engine-core] logging: add proper logging in case engine decides not ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.4
Assignee: lpeer
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 15:33 UTC by Haim
Modified: 2016-02-10 16:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-12 07:36:01 UTC
oVirt Team: Storage


Attachments (Terms of Use)
rhevm log. (183.78 KB, application/x-gzip)
2012-01-24 15:33 UTC, Haim
no flags Details

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.


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