Bug 1429643
Summary: | virt-v2v should depend on OVMF/AAVMF | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Richard W.M. Jones <rjones> |
Component: | libguestfs | Assignee: | Pino Toscano <ptoscano> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.4 | CC: | juzhou, kuwei, mxie, mzhan, ptoscano, tzheng, xiaodwan |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | V2V | ||
Fixed In Version: | libguestfs-1.36.2-2.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 22:13:55 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: | |||
Bug Depends On: | 1329559 | ||
Bug Blocks: | 1429506 |
Description
Richard W.M. Jones
2017-03-06 18:28:49 UTC
Verify the bug with below builds: virt-v2v-1.36.2-2.el7.x86_64 libguestfs-1.36.2-2.el7.x86_64 Steps: 1:Make sure OVMF and virt-v2v installed,then run below command: # rpm -qR virt-v2v | grep -i vmf OVMF 2:Make sure no OVMF and virt-v2v package removed, then re-install virt-v2v . # yum install virt-v2v ****************** Resolving Dependencies --> Running transaction check ---> Package virt-v2v.x86_64 1:1.36.2-2.el7 will be installed --> Processing Dependency: OVMF for package: 1:virt-v2v-1.36.2-2.el7.x86_64 --> Running transaction check ---> Package OVMF.noarch 0:20170228-1.gitc325e41585e3.el7 will be installed --> Finished Dependency Resolution ***************** Results:I think virt-v2v is depending on OVMF in this version build. So , I think we could move this 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. https://access.redhat.com/errata/RHBA-2017:2023 |