Description of problem:
When the user moved the Storage Domain to maintenance, all the entities related to the Storage Domain should be updated in the OVF_STORE disk
Version-Release number of selected component (if applicable):
50% (Depends on the scheduler and the minutes in the config value)
Steps to Reproduce:
1. Add a VM and a disk
2. immediately move the Storage Domain to maintenance.
3. Try to import the Storage Domain to another setup
The VM will not be part of the unregistered entities
The VM should be part of the unregistered entities
please verify dependent BZ #1147251
Liron, please add doctext to explain how this addects putting a domain in maintenance.
Maintenance storage domain triggers an UploadStreamVDSCommand for the OVF store disk. All the entities that exist on that domain are availeable to be registered in the new DC.
2014-12-16 10:17:47,416 INFO [org.ovirt.engine.core.bll.storage.DeactivateStorageDomainWithOvfUpdateCommand] (org.ovirt.thread.pool-7-thread-6) [6e60e28b] Running command: DeactivateStorageDomainWithOvfUpdateCommand internal: false. Entities affected : ID: 0f4c7dbf-8989-40e1-8988-ed0717429db9 Type: StorageAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN
2014-12-16 10:17:47,560 INFO [org.ovirt.engine.core.bll.ProcessOvfUpdateForStorageDomainCommand] (org.ovirt.thread.pool-7-thread-6) [55f550d7] Running command: ProcessOvfUpdateForStorageDomainCommand internal: true. Entities affected : ID: 0f4c7dbf-8989-40e1-8988-ed0717429db9 Type: Storage
Verified using rhev3.5 vt13.3
Elad, thanks for verifying! I suggest further check for this bug - increase StorageDomainOvfStoreCount and see that more stores are created and updated on the deactivation.
OVF_UPDATE is executed the number of times specified for the domain that is being deactivated
RHEV-M 3.5.0 has been released, closing this bug.