Bug 1143883

Summary: warning shows when converting rhel7 guest:virt-v2v:could not update grub2 console: aug_get: no matching node (ignored)
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: codong, dyuan, juzhou, mbooth, mzhan, ptoscano, rjones
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: V2V
Fixed In Version: libguestfs-1.27.49-1.1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 13:45:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Debug info about converting rhel7 guest none

Description tingting zheng 2014-09-18 08:07:17 UTC
Created attachment 938787 [details]
Debug info about converting rhel7 guest

Description
warning shows when converting rhel7 guest:virt-v2v:could not update grub2 console: aug_get: no matching node (ignored)

Version:
libguestfs-1.27.48-1.1.el7.x86_64
virt-v2v-1.27.48-1.1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a rhel7 guest.

2.Use virt-v2v to convert rhel7 guest,warning shows:
virt-v2v: warning: could not update grub2 console: aug_get: no matching
node (ignored)

# virt-v2v -ic xen+ssh://10.66.106.64 -os default rhel7 -of raw
[   0.0] Opening the source -i libvirt -ic xen+ssh://10.66.106.64 rhel7
[  17.0] Creating an overlay to protect the source from being modified
[  31.0] Opening the overlay
[  53.0] Initializing the target -o libvirt -os default
[  53.0] Inspecting the overlay
[  62.0] Checking for sufficient free disk space in the guest
[  62.0] Estimating space required on target for each disk
[  62.0] Converting Red Hat Enterprise Linux Server release 7.0 Beta (Maipo) to run on KVM
virt-v2v: warning: could not update grub2 console: aug_get: no matching
node (ignored)
[ 123.0] Mapping filesystem data to avoid copying unused and blank areas
[ 124.0] Closing the overlay
[ 125.0] Copying disk 1/1 to /var/lib/libvirt/images/rhel7-sda (raw)
    (100.00/100%)
[ 207.0] Creating output metadata
Pool default refreshed

Domain rhel7 defined from /tmp/v2vlibvirtd8e625.xml

[ 207.0] Finishing off

Actual results:
Warning shows as description.

Expected results:
No such warning shows.

Additional info:
Attached the detailed log file.

Comment 2 Richard W.M. Jones 2014-09-18 13:14:31 UTC
I don't know how serious this is.  It *is* reproducible easily however:

$ virt-builder rhel-7.0
$ virt-v2v -i disk rhel-7.0.img -o null
[   0.0] Opening the source -i disk rhel-7.0.img
[   0.0] Creating an overlay to protect the source from being modified
[   0.0] Opening the overlay
[   8.0] Initializing the target -o null
[   8.0] Inspecting the overlay
[  11.0] Checking for sufficient free disk space in the guest
[  11.0] Estimating space required on target for each disk
[  11.0] Converting Red Hat Enterprise Linux Server release 7.0 (Maipo) to run on KVM
virt-v2v: warning: could not update grub2 console: aug_get: no matching 
node (ignored)
[  41.0] Mapping filesystem data to avoid copying unused and blank areas
[  42.0] Closing the overlay
[  43.0] Copying disk 1/1 to /var/tmp/null.ggDLGx/sda (raw)
    (100.00/100%)
[  46.0] Creating output metadata
[  46.0] Finishing off

Comment 3 Richard W.M. Jones 2014-09-18 13:56:06 UTC
I think this was a bug in old virt-v2v.  Yay!

The fix is:

https://github.com/libguestfs/libguestfs/commit/035f47cdde4052e77613c77d2e5e0f24dbab082f

Comment 4 tingting zheng 2014-09-19 06:26:16 UTC
Tested the bug with:
libguestfs-1.27.49-1.1.el7.x86_64
virt-v2v-1.27.49-1.1.el7.x86_64

Use virt-v2v to convert a rhel7 guest,there is no such warning info shows,so move the bug to VERIFIED.

Comment 6 errata-xmlrpc 2015-03-05 13:45:15 UTC
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/RHBA-2015-0303.html