Hide Forgot
New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/59e5de4f03c21eaaa584ef5a2ab933bd4ab4a8c5 commit 59e5de4f03c21eaaa584ef5a2ab933bd4ab4a8c5 Author: Keenan Brock <keenan@thebrocks.net> AuthorDate: Fri Jun 14 18:03:37 2019 -0400 Commit: Keenan Brock <keenan@thebrocks.net> CommitDate: Fri Jun 14 18:03:37 2019 -0400 Merge pull request #18860 from djberg96/conversion_host_throttling [V2V] Modify active_tasks so that it always reloads (cherry picked from commit 660387c242a7581405ad85280370cd77317aac36) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1721117 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1721118 app/models/conversion_host.rb | 5 +- lib/infra_conversion_throttler.rb | 13 +- 2 files changed, 15 insertions(+), 3 deletions(-)
Verified on CFME-5.10.6.1/RHV-4.3.4.3-0.1.el7 Checked with 2 cases: 1. VMware->RHV migration, VDDK, of 20 VMs/100GB disk, and Provider max concurrent VM migrations: 20, and Max concurrent VM migrations, 2 conversion hosts, per conversion host: 10. Storage type: VMware- ISCSI, RHV- FC. VMs were distributed evenly, between the 2 conversion hosts, 10:10. 2. Same env, but with 2 conversion hosts, per conversion host: 5. result: On first round, the VMs were distributed evenly, 5:5. then 1 vM failed on Bug 1719689 - [v2v][RHV][vddk] 1 out of 10 VMs failed migration, on CFME failed to read the state file. As a result 1 additional VM started to be migrated to the conversion host, on which the first VM failed migration. So the distribution became 5:5, again. After the first round ended, the second round distribution was 4:5 This is even distribution, since only 9 VMs were left to migrate. the second round ended with a second VM migration failure, on Bug 1724040 - [v2v][Scale][RHV] VM migration fail on "start is not permitted at state running"
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-2019:1644