Bug 1855213
| Summary: | Skipping progress update for unknown disk | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | mheppler |
| Component: | v2v-conversion-host | Assignee: | Tomáš Golembiovský <tgolembi> |
| Status: | CLOSED ERRATA | QA Contact: | Md Nadeem <mnadeem> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.3.9 | CC: | ahadas, bthurber, fdewaley, fdupont, mavital, michal.skrivanek, mnadeem, rdlugyhe, tgolembi |
| Target Milestone: | ovirt-4.3.11 | Keywords: | ZStream |
| Target Release: | 4.3.11 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | v2v-conversion-host-1.16.2-2.el7ev | Doc Type: | Bug Fix |
| Doc Text: |
After updating the packages on a conversion host, it stopped displaying conversion progress. The current release fixes this issue. The conversion host reports its progress performing conversions, including on the latest RHEL 7-based hosts.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-30 10:09:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1856952 | ||
| Bug Blocks: | |||
|
Description
mheppler
2020-07-09 09:04:55 UTC
Would it be possible to attach the virt-v2v and virt-v2v-wrapper log files to this BZ, please? The BZ is verified with RHV version 4.3.11 and CFME 5.11.7 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 (Red Hat Virtualization RHEL Host (ovirt-host) 4.3.11), 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-2020:4113 Due to QE capacity, we are not going to cover this issue in our automation |