Description of problem: The customer did not remove the VMWare provider before rebuilding vcenter. This has caused CloudForms to see the hosts as new and is appending the hostnames with "-2". I have tested this by adding a provider, removing the provider and re-adding. The hosts were linked back up and had matching ems_ref values This is not the case with the customer as their hosts output shows the appending/duplicate hosts with a different ems_ref Version-Release number of selected component (if applicable): 5.9.8 How reproducible: Steps to Reproduce: 1.Add provider 2.Rebuild hosts through provider without removing provider from CloudForms first 3. Actual results: Expected results: Additional info:
https://github.com/ManageIQ/manageiq/pull/18856
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/701f6c0850fb143140eb62bdee9685a3781e9ec7 commit 701f6c0850fb143140eb62bdee9685a3781e9ec7 Author: Adam Grare <agrare> AuthorDate: Thu Jun 27 11:30:52 2019 -0400 Commit: Adam Grare <agrare> CommitDate: Thu Jun 27 11:30:52 2019 -0400 Reconnect archived hosts with a different ems_ref If a vCenter is rebuilt all imported hosts will have different ems_refs. This shouldn't prevent these hosts from being reconnected. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1719399 app/models/ems_refresh/save_inventory_infra.rb | 4 +- spec/models/ems_refresh/save_inventory_infra_spec.rb | 29 +- 2 files changed, 25 insertions(+), 8 deletions(-)
ON CFME 5.11.0.16 I tested the scenario using comment 10 and it worked as expected. No more host duplication.
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:4199