Bug 817799 - ovirt-engine-backend [Auto-Recovery]: when deactivating master domain and jboss restarts we start the domain automatically on jboss startup
Summary: ovirt-engine-backend [Auto-Recovery]: when deactivating master domain and jbo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
: 3.1.0
Assignee: mkublin
QA Contact: Haim
URL:
Whiteboard: storage
Depends On: 829275
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-01 10:50 UTC by Dafna Ron
Modified: 2016-02-10 16:44 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-11 07:08:19 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log (8.36 KB, application/x-xz)
2012-05-01 10:50 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2012-05-01 10:50:24 UTC
Created attachment 581349 [details]
log

Description of problem:

I deactivated the master domain and restarted jboss while domain was in image locked.
when jboss started the domain was started automatically. 

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

si2.1

How reproducible:

100%

Steps to Reproduce:
1. deactivate master domain
2. restart jboss while domain is in image locked 
3.
  
Actual results:

when jboss starts we activate the domain automatically

Expected results:

we should not activate the domain

Additional info: log

Comment 1 Ayal Baron 2012-06-10 12:27:05 UTC
what do you mean it was started automatically?
did deactivate fail (because of the restart) - if so then this sounds fine to me.
If it succeeded then was master migrated to a different domain?

Comment 2 Dafna Ron 2012-06-10 12:41:30 UTC
deactivate did not fail because of the restart. 
deactivate was already sent to vdsm and completed, jboss restart should have no effect on commands that were already sent to vdsm
it seemed that the autorecovery started the domain since when jboss starts the domain status was checked and we start it. 

but, there is a bug https://bugzilla.redhat.com/show_bug.cgi?id=829275 for the domain status's that might be related to this bug

Comment 3 Itamar Heim 2012-06-10 14:05:55 UTC
kublin - related to bug 829275?

Comment 4 mkublin 2012-06-11 07:08:19 UTC
Actually, it is not related to auto recovery and these behaviour is not bug.
We are saving a previous status of domain which is UP, when restart happenes we are trying to return to previous status which is UP, becuase of we have not any idea when restart is occurred. After that if we will have a different status from host they will report these to us and we will handle domain in appropriate way.

To see that status of domain was changed by compensation mechanism can be see at logs:
2012-05-01 12:18:38,210 INFO  [org.ovirt.engine.core.bll.storage.DeactivateStorageDomainCommand] (MSC service thread 1-1) Command [id=647f71f2-f757-4cf2-b06e-3617e63b6d98]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.storage_pool; snapshot: EntityStatusSnapshot [id=fd4053d0-d4a6-4402-beaa-d923c252e7f8, status=Up].
2012-05-01 12:18:38,237 INFO  [org.ovirt.engine.core.bll.storage.DeactivateStorageDomainCommand] (MSC service thread 1-1) Command [id=647f71f2-f757-4cf2-b06e-3617e63b6d98]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.storage_pool_iso_map; snapshot: EntityStatusSnapshot [id=storagePoolId = fd4053d0-d4a6-4402-beaa-d923c252e7f8, storageId = b5f3c87a-2647-4353-9553-34d5a5e00f0a, status=Active].
2012-05-01 12:18:38,289 INFO  [org.ovirt.engine.core.bll.Backend] (MSC service thread 1-1) Running compensation on startup for Command : org.ovirt.engine.core.bll.storage.DeactivateStorageDomainCommand , Command Id : 647f71f2-f757-4cf2-b06e-3617e63b6d98


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