Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
virt-v2v show the warning info after convert rhel4u8 guest if comment a line in the fstab
Version-Release number of selected component (if applicable):
virt-v2v-0.7.1-3.el6.x86_64
libguestfs-1.7.17-12.el6.x86_64
libguestfs-*-1.7.17-12.el6.x86_64
libvirt-0.8.7-6.el6.x86_64
febootstrap-2.11-6.el6.x86_64
hivex-1.2.4-3.el6.x86_64
libguestfs-winsupport-1.0-5.el6.x86_64
augeas-libs-0.7.2-4.el6.x86_64
virtio-win-1.1.16-1.el6.noarch
How reproducible:
always
Steps to Reproduce:
before conversion make sure that comment the swap line in the fstab
1.#virt-v2v -ic xen+ssh://10.66.72.123 -op sdb1 -b breth0 rhel4u8-64b-pw-raw-intel
rhel4u8-64b-pw-raw-intel.img: 100% [==============================================================================================================]D 0h04m52s
unknown filesystem #/dev/VolGroup00/LogVol01
virt-v2v: rhel4u8-64b-pw-raw-intel configured with virtio drivers
2.check the guest fstab ,there is no different between before and after conversion.
#cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
#/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
Actual results:
unknown filesystem #/dev/VolGroup00/LogVol01
Expected results:
no need to show the warning because this is juest a comments
Additional info:
it can be reproduced with the guest rhel6 .
This is pretty minor. I want to minimise churn at the moment, so I'm moving this to 6.2.
Comment 4Richard W.M. Jones
2011-09-20 14:20:41 UTC
This should be ready for testing.
There is no fix in libguestfs required AFAIK. It
should just work because virt-v2v was changed to use
the new libguestfs core inspection API (ie. bug 672831).
So to test this, just use the latest libguestfs / virt-v2v
combo from RHEL 6.2.
Verified the bug with the following packages:
virt-v2v-0.8.3-5.el6.x86_64
libvirt-0.9.4-11.el6.x86_64
libguestfs-1.7.17-26.el6.x86_64
Steps:
1.comment the swap line in the fstab file of rhel4u8 guest.
2.Use virt-v2v to convert the guest.
#virt-v2v -ic xen+ssh://10.66.72.123 -os default -b rhevm rhel4u8-64b-pw-raw-intel
rhel4u8-64b-pw-raw-intel.img: 100% [==============================================================================]D 0h03m46s
virt-v2v: rhel4u8-64b-pw-raw-intel configured with virtio drivers.
3.After conversion,boot the guest and check the fstab file.
#cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
#/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
There is no warning showed when using virt-v2v,so change the status to VERIFIED.
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.
http://rhn.redhat.com/errata/RHSA-2011-1615.html