Bug 1138124
Summary: | [Import Domain] When a Storage Domain is moved to maintenance the OVF store disk should be updated synchronously | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Maor <mlipchuk> |
Component: | ovirt-engine | Assignee: | Liron Aravot <laravot> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Elad <ebenahar> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.5.0 | CC: | adevolder, amureini, ebenahar, ecohen, gklein, iheim, laravot, lpeer, ogofen, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon |
Target Milestone: | --- | Flags: | amureini:
Triaged+
|
Target Release: | 3.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | storage | ||
Fixed In Version: | org.ovirt.engine-root-3.5.0-25 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Data Centers in version 3.5 support OVF stores disk on any domain that contains the OVF data related to the domain (which means - VMs/Templates that has at least on disk on the domain or diskless VMs/Templates).
The OVF stores are created (the number of stores is defined by the StorageDomainOvfStoreCount config value) and updated by the OvfDataUpdater on a regular basis on intervals defined by OvfUpdateIntervalInMinutes config value.
Therefore When a domain is being moved to maintenance it's OVF data might not be up to date.
Consequence:
The domain moves to maintenance status, but the OVF data on it's OVF stores is not updated and there might be less OVF stores then defined.
Fix:
When a Storage Domain is being moved to maintenance OVF stores on it should be created/updated.
Result:
When a Storage Domain is being moved to maintenance OVF stores on it are created/updated.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1147251 |
Description
Maor
2014-09-04 06:34:32 UTC
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 rhevm-3.5.0-0.25.el6ev.noarch 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. RHEV-M 3.5.0 has been released, closing this bug. |