Currently the VimBrokerWorker uses WaitForUpdates to maintain a cache of inventory and makes it available to be queried by a RefreshWorker while doing an EmsRefresh. Targeted refreshes are initiated through parsing of Events caught by the EventCatcher and a refresh is queued by an automate method. This leads to a relatively large turnaround time from something changing on the provider until it is persisted in the database. It is possible to instead of using events to trigger targeted refreshes to parse the UpdateSet returned by WaitForUpdates and save that to the database. This reduces the total time to process targeted refreshes. This is available today as a prototype through settings (prototype/ems_vmware/update_driven_refresh) but is not yet completely at feature parity with existing EmsRefresh.
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
Adding some of the recent PRs here: https://github.com/ManageIQ/manageiq-providers-vmware/pull/265 https://github.com/ManageIQ/manageiq-providers-vmware/pull/263 https://github.com/ManageIQ/manageiq-providers-vmware/pull/262 https://github.com/ManageIQ/manageiq-providers-vmware/pull/259 https://github.com/ManageIQ/manageiq-providers-vmware/pull/258 https://github.com/ManageIQ/manageiq-providers-vmware/pull/256 https://github.com/ManageIQ/manageiq-providers-vmware/pull/255 https://github.com/ManageIQ/manageiq-providers-vmware/pull/254 https://github.com/ManageIQ/manageiq-providers-vmware/pull/251 https://github.com/ManageIQ/manageiq-providers-vmware/pull/248 https://github.com/ManageIQ/manageiq-providers-vmware/pull/243 https://github.com/ManageIQ/manageiq-providers-vmware/pull/240 https://github.com/ManageIQ/manageiq-providers-vmware/pull/236 https://github.com/ManageIQ/manageiq-providers-vmware/pull/235 https://github.com/ManageIQ/manageiq-providers-vmware/pull/234 https://github.com/ManageIQ/manageiq-providers-vmware/pull/233
https://github.com/ManageIQ/manageiq-providers-vmware/pull/270 https://github.com/ManageIQ/manageiq-providers-vmware/pull/266
https://github.com/ManageIQ/manageiq/pull/17531
At this point vmware streaming refresh is ready to test, setting prototype/ems_vmware/update_driven_refresh to true and restarting the appliance will enable streaming refresh for vmware.
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/RHSA-2019:0212