Bug 1430240 - [Docs] [RFE] [Admin] [VMM] A description of the new VM import logs must be provided
Summary: [Docs] [RFE] [Admin] [VMM] A description of the new VM import logs must be pr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.1-1
: ---
Assignee: Emma Heftman
QA Contact: Tahlia Richardson
URL:
Whiteboard:
Depends On: 1350465
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-08 06:42 UTC by Andrew Dahms
Modified: 2019-05-07 13:15 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-03 05:57:59 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Dahms 2017-03-08 06:42:03 UTC
In Red Hat Virtualization 4.1, logs of virtual machine import tasks are now kept in the '/var/log/vdsm/import' on hosts. A description of this new log location must be added to 'Red Hat Virtualization Host Log Files' in the Administration Guide.

See the doc text in BZ#1350465 for more details.

Comment 1 Lucy Bopf 2017-03-23 07:04:40 UTC
Assigning to Emma for review.

Comment 2 Emma Heftman 2017-03-26 10:12:23 UTC
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.

Comment 3 Emma Heftman 2017-03-26 10:13:50 UTC
(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

Comment 4 Emma Heftman 2017-03-26 10:21:34 UTC
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.

Comment 9 Tomas Jelinek 2017-03-29 12:49:36 UTC
(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.

Comment 10 Tomáš Golembiovský 2017-03-29 13:28:53 UTC
(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.

Comment 11 Tomáš Golembiovský 2017-03-29 13:36:13 UTC
(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.

Comment 12 Tomáš Golembiovský 2017-03-29 14:17:54 UTC
(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.


Note You need to log in before you can comment on or make changes to this bug.