Created attachment 1554455 [details] issue.png Description of problem: Max per host setting doesn't honor limits from UI Version-Release number of selected component (if applicable): 5.10.3.1.20190408182335_d0fa1a0 How reproducible: 100% Steps to Reproduce: 1. Set max per host number in UI (let say 1 is limit) 2. Run migration (let say 2 migration) Actual results: Max per host not working Expected results: It should work Additional info: We did not had this issue with 5.10.3.0 so I hope it should work on that. We are still checking it.
We saw behavior where if we have limit=2, 3 migrations are getting running currently. So if we need to to restrict host limit we can also use upper limit i.e. provider limit. That means as a workaround by setting host_limit=2 and provider_limit=2 we can run 2 migration and other can get throttled since provider limit is working.
We've been digging into this but haven't completely nailed it down. Initial investigation suggests a race condition within this block: https://github.com/ManageIQ/manageiq/blob/master/lib/infra_conversion_throttler.rb#L6-L13 Still digging...
We'll need to reproduce once conversion host management works, i.e. on a 5.10.5.x build. If a fix is needed, we'll target 5.10.6.
In progress: https://github.com/ManageIQ/manageiq/pull/18860
Created attachment 1594260 [details] expected_throttling.png