Bug 716511

*** Bug 705258 has been marked as a duplicate of this bug. ***

IIRC, the biggest roadblock used to be discovery and identification of new/existing objects on SD - but that was fixed in 3.2 (bug 886133).

*** Bug 1015321 has been marked as a duplicate of this bug. ***

*** Bug 1029801 has been marked as a duplicate of this bug. ***

*** Bug 1025788 has been marked as a duplicate of this bug. ***

*** Bug 1063269 has been marked as a duplicate of this bug. ***

hi Maor,
 This bug has been flagged for release notes. Please select the correct Doc Type and provide the doc text ASAP for this bug to make it in the 3.5 Beta Manager Release Notes. If this bug is not required for release notes, please set the require_release_note flag to -.

Cheers,
Julie

Julie can you please provide doc ack for this bug or know who provides it, as I want to run the final tests and verify soon after BZ #1136902 dependence is cleared

(In reply to Ori Gofen from comment #20)
> Julie can you please provide doc ack for this bug or know who provides it,
> as I want to run the final tests and verify soon after BZ #1136902
> dependence is cleared

Hi Ori,
   Thanks for looping me in. As you can see in the email thread I forwarded you, the feature documentation is currently blocked as the docs team is running into errors when testing the feature out. If anyone can provide more insight, please reach out to Andrew Dahms (adahms). 

If you are only referring to the doc text/release note flag part for this bug, it has been added to the 3.5 Beta Release Notes already:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5-Beta/html/Manager_Release_Notes/Storage_Features3.html

and I've pasted back the doc text in the doc text field of this bug. Bugzilla will automatically set the flag to +.

Kind regards,
Julie

I have seen it, please Have them ping me with problems such as they've encountered, as it could very well may be bugs.

please be aware to the documented gaps:
1) import a domain which  originally created on previous versions (V < 3.5) is        not yet supported.
2) detach attach(or import) domain as a master domain is not yet supported.
3) glusterfs is not yet supported
4) import entities with objects on mixed storage domains is not yet supported

**
please be aware of engine-config OvfUpdateIntervalInMinutes is set to a couple of minutes so the entities created will be updated during a reasonable interval 
**
If it's possible, I would like you'r team to attach those logs here with the correct flow of execution.

thanx a bunch for the mail, I have learned from it that the documentation probably isn't good enough.

Maor, just making sure that you read this.

(In reply to Ori Gofen from comment #22)
> I have seen it, please Have them ping me with problems such as they've
> encountered, as it could very well may be bugs.
> 
> please be aware to the documented gaps:
> 1) import a domain which  originally created on previous versions (V < 3.5)
> is        not yet supported.

This will not be supported since the OVF_STORE disk is a crucial entity for the recovery process. and OVF_STORE feature is only supported in 3.5 Data Centers

> 2) detach attach(or import) domain as a master domain is not yet supported.

This will not be supported for 3.5, but the plan is that a CDA message should be performed when trying to do so (see http://gerrit.ovirt.org/#/c/34239/)

> 3) glusterfs is not yet supported

should be supported, Import of a glusterfs data Storage is documented at http://www.ovirt.org/Features/ImportStorageDomain#Work_flow_for_importing_GlusterFS_Storage_Domain_-_UI_flow

> 4) import entities with objects on mixed storage domains is not yet supported

import of VMs/Templates with disks residing on Multiple Storage Domain is supported and can be imported while the Storage Domains are valid and active.

> 
> **
> please be aware of engine-config OvfUpdateIntervalInMinutes is set to a
> couple of minutes so the entities created will be updated during a
> reasonable interval 
> **
> If it's possible, I would like you'r team to attach those logs here with the
> correct flow of execution.
> 
> thanx a bunch for the mail, I have learned from it that the documentation
> probably isn't good enough.
> 
> Maor, just making sure that you read this.

I still waiting for the logs of Andrew to investigate what was happened.

Hi Andrew, Are there any news with the engine/vdsm logs?
Can you please describe the reproduce steps and the error which you got?

Thanks

Hi Maor,

Thank you for raising the needinfo request!

I have done some testing today, and have had a little success. I will work with the feature a little more and see what I can document.

I will have some content for you to review soon, or will provide further information on any issues I encounter as soon as I can.

Kind regards,

Andrew

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0158.html