Bug 1430240
| Summary: | [Docs] [RFE] [Admin] [VMM] A description of the new VM import logs must be provided | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Andrew Dahms <adahms> |
| Component: | Documentation | Assignee: | Emma Heftman <eheftman> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tahlia Richardson <trichard> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | gklein, lbopf, lsurette, rbalakri, srevivo, tgolembi, tjelinek, trichard, ykaul |
| Target Milestone: | ovirt-4.1.1-1 | Keywords: | FutureFeature |
| 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: | 2017-04-03 05:57:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1350465 | ||
| Bug Blocks: | |||
|
Description
Andrew Dahms
2017-03-08 06:42:03 UTC
Assigning to Emma for review. Hi Tomas, I'm document the log file that is connected to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1430240 Could you please let me know whether it is relevant for the following import procedure: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1-beta/html-single/administration_guide/#sect-Importing_Existing_Storage_Domains Thanks. (In reply to Emma Heftman from comment #2) > Hi Tomas, I'm document the log file that is connected to this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1430240 > > Could you please let me know whether it is relevant for the following import > procedure: > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1- > beta/html-single/administration_guide/#sect- > Importing_Existing_Storage_Domains > > Thanks. In section 8.6.5. Importing Virtual Machines from Imported Data Storage Domains Alternatively, if it is related to this knowledgebase article, I'm not sure whether this should be part of the documentation at all, as the virt-v2v feature seems only to be described as part of the knowledgebase. https://access.redhat.com/articles/1351473 Converting Virtual Machines from Other Hypervisors to KVM with virt-v2v in RHEL 7 The documentation references this article from here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1-beta/html-single/virtual_machine_management_guide/#sect-Exporting_and_Importing_Virtual_Machines_and_Templates Section 6.12. Exporting and Importing Virtual Machines and Templates As stated, it only references the virt-v2v tool. Hi Tomas Please review the updated log file section in the Admin Guide: http://file.tlv.redhat.com/~eheftman/bz1430240/Admin/#Red_Hat_Enterprise_Virtualization_Host_Log_Files1 And The note that I added about the log file in the following sections of the Virtual Machine Management Guide: http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/#Importing_a_Virtual_Machine_from_a_VMware_Provider http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/#Importing_a_Virtual_Machine_from_Xen http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/#Importing_a_Virtual_Machine_from_KVM (In reply to Emma Heftman from comment #8) > Hi Tomas > Please review the updated log file section in the Admin Guide: > > http://file.tlv.redhat.com/~eheftman/bz1430240/Admin/ > #Red_Hat_Enterprise_Virtualization_Host_Log_Files1 > I think you added the "/var/log/vdsm/import.log" - looks good. > > And > > The note that I added about the log file in the following sections of the > Virtual Machine Management Guide: > > http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/ > #Importing_a_Virtual_Machine_from_a_VMware_Provider > > http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/ > #Importing_a_Virtual_Machine_from_Xen > > http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/ > #Importing_a_Virtual_Machine_from_KVM I would rephrase this notes to: If a failure occurs during the import process, refer to the /var/log/vdsm/import.log and to /var/log/vdsm/vdsm.log file on the proxy host for details. (In reply to Emma Heftman from comment #3) > (In reply to Emma Heftman from comment #2) > > Hi Tomas, I'm document the log file that is connected to this bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1430240 > > > > Could you please let me know whether it is relevant for the following import > > procedure: > > > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1- > > beta/html-single/administration_guide/#sect- > > Importing_Existing_Storage_Domains > > > > Thanks. > > In section 8.6.5. Importing Virtual Machines from Imported Data Storage > Domains No, this one is not relevant. (In reply to Emma Heftman from comment #4) > Alternatively, if it is related to this knowledgebase article, I'm not sure > whether this should be part of the documentation at all, as the virt-v2v > feature seems only to be described as part of the knowledgebase. > > https://access.redhat.com/articles/1351473 Converting Virtual Machines from > Other Hypervisors to KVM with virt-v2v in RHEL 7 > > The documentation references this article from here: > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1- > beta/html-single/virtual_machine_management_guide/#sect- > Exporting_and_Importing_Virtual_Machines_and_Templates > > Section 6.12. Exporting and Importing Virtual Machines and Templates > > As stated, it only references the virt-v2v tool. This one is not relevant either. (In reply to Tomas Jelinek from comment #9) > (In reply to Emma Heftman from comment #8) > > Hi Tomas > > Please review the updated log file section in the Admin Guide: > > > > http://file.tlv.redhat.com/~eheftman/bz1430240/Admin/ > > #Red_Hat_Enterprise_Virtualization_Host_Log_Files1 > > > > I think you added the "/var/log/vdsm/import.log" - looks good. Actually this is not correct. /var/log/vdsm/import is a directory and each attempt to import a VM creates a log file in that directory. The name of each file is of the form "import-<UUID>-<stamp>.log" where <UUID> is the UUID of the VM being imported and <stamp> is a date/time when the import started. > > > > > And > > > > The note that I added about the log file in the following sections of the > > Virtual Machine Management Guide: > > > > http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/ > > #Importing_a_Virtual_Machine_from_a_VMware_Provider > > > > http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/ > > #Importing_a_Virtual_Machine_from_Xen > > > > http://file.tlv.redhat.com/~eheftman/bz1430240/Virtual/ > > #Importing_a_Virtual_Machine_from_KVM > > I would rephrase this notes to: > If a failure occurs during the import process, refer to the > /var/log/vdsm/import.log and to /var/log/vdsm/vdsm.log file on the proxy > host for details. I agree with Tomas here, vdsm.log should be mentioned too. Published documentation: Administration Guide: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1-beta/html-single/administration_guide/#Red_Hat_Enterprise_Virtualization_Host_Log_Files1 Virtual Machine Management Guide: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1-beta/html-single/virtual_machine_management_guide/#sect-Exporting_and_Importing_Virtual_Machines_and_Templates Section, 6.12.4, 6.12.5 and 6.12.6 |