Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1572357

Summary: [Docs][Admin][VMM] Make clear the steps to import a VM from Local Storage Domain
Product: Red Hat Enterprise Virtualization Manager Reporter: Javier Coscia <jcoscia>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED DUPLICATE QA Contact: rhev-docs <rhev-docs>
Severity: medium Docs Contact:
Priority: low    
Version: 4.1.10CC: lsurette, rbarry, sgoodman, srevivo
Target Milestone: ovirt-4.4.1Keywords: Documentation, Task, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-26 11:28:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Javier Coscia 2018-04-26 19:34:43 UTC 
Description of problem:

There're no steps in admin guide nor in VMM guide which lists the steps required to import a VM from a Local Storage Domain

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

4.x


Request: 

Add a section in the admin guide on how to import a local storage domain into a DC with Storage Type: Local

Storage > Import Domain > Data Center (select one with Local type) > Storage Type Local on Host > Give it a name and a path accessible for host listed in Host to Use box > OK

Activate it: Storage > Domain > Data Center > Activate



Add a section in the VMM guide on how to import the VM from previous steps

Storage > Domain > VM Import > select VM > click on Import button and follow the normal steps to import a VM.
Comment 1 Ryan Barry 2019-01-21 14:54:28 UTC 
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both
Comment 4 Steve Goodman 2019-11-26 11:28:17 UTC 
Closing this as a duplicate of bug 1548850. I already address this issue in that bug.

*** This bug has been marked as a duplicate of bug 1548850 ***