Description of problem: two VMDB ESX host instances exist in the same VMDB. one is from BEfore a VMWARE maintenance and the other is after maintenance is complete. the host names for the two entries are identical as are the ip addresses. the VMware host id and the HOSTS table ids are different. However, the display name of the newer host is being incremented as follows: original name: 'VMH-050' starts being displayed in an incrementing fashion as "VMH-050 - 2" up through "VMH-051 - 0" and then restarts. Notice that the final digit of the name has incremented from "0" to "1". A second instance in the same customer with the host name of "VMH-051" is behaving in a similar manner. Version-Release number of selected component (if applicable):5.5.2.4 How reproducible: Steps to Reproduce: 1. perform emsrefres in VMware environment with deliberately backlevel ESX host 2. after two refreshes complete, place ESX host into maintenance mode and update the ESX software to a new level (like 5.1 to 5.5.0) 3. bring updated host out of maintenance mode and perform refresh 4. allow multiple refreshes to occur and monitory the display name Actual results: display name increments as described above Expected results: display name should not increment Additional info: two greps of files are provided one for each of the two ESX hosts in the customer environment where this has been encountered
Created attachment 1148232 [details] sample evm.log lines showing how the display name become altered for ip address 10.2.2230.15
Created attachment 1148233 [details] sample evm.log lines showing how the display name become altered for ip address 10.2.230.16
Greg and Adam, I have confirmed with the customer who reported this issue that the hosts which are duplicated were significantly changed (new hardware and software) and reintroduced back into the CFME environment. What is troubling from a provisioning perspective is that the host name ( referred to be me as 'display name') seems to be changing each time an emsrefresh is executed making the name a moving target so that if provisioning were set up to provision to a fixed name, it would fail 9 times out of 10 because of the way the host display names are changing. Tom Hennessy
https://github.com/ManageIQ/manageiq/pull/8227
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/40961a3cc401325b458d458b749b7a8b553e5d32 commit 40961a3cc401325b458d458b749b7a8b553e5d32 Author: Adam Grare <agrare> AuthorDate: Mon Apr 25 12:23:49 2016 -0400 Commit: Adam Grare <agrare> CommitDate: Mon Apr 25 16:53:35 2016 -0400 Fix host name collision incrementing every refresh When saving a host, check to see if the found.name is the current host name plus a duplicate host name suffix. This prevents the host name from being constantly incremented every ems_refresh. https://bugzilla.redhat.com/show_bug.cgi?id=1328145 app/models/ems_refresh/save_inventory_infra.rb | 12 +++++++++--- spec/models/ems_refresh/save_inventory_infra_spec.rb | 11 +++++++++++ 2 files changed, 20 insertions(+), 3 deletions(-)
https://github.com/ManageIQ/manageiq/pull/8473
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-2016:1348