Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1328145 - Provisioning failing in production due to ESX Hosts with Identical host names in the VMDB causing the DISPLAY name to dynamically increment over multiple refreshes
Provisioning failing in production due to ESX Hosts with Identical host names...
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.5.0
x86_64 Linux
high Severity high
: GA
: 5.6.0
Assigned To: Adam Grare
Alex Newman
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-04-18 10:58 EDT by Thomas Hennessy
Modified: 2016-08-26 10:49 EDT (History)
9 users (show)

See Also:
Fixed In Version: 5.6.0.5
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Management Engine, provisioning failed in production due to ESX hosts with identical host names in the VMDB causing the display name to dynamically increment over multiple refreshes. This patch when saving a host now checks 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 with every ems_refresh which has now resolved the issue.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-29 11:50:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
sample evm.log lines showing how the display name become altered for ip address 10.2.2230.15 (20.57 KB, text/plain)
2016-04-18 11:02 EDT, Thomas Hennessy 		no flags Details
sample evm.log lines showing how the display name become altered for ip address 10.2.230.16 (58.72 KB, text/plain)
2016-04-18 11:07 EDT, Thomas Hennessy 		no flags Details
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 14:50:04 EDT

  None (edit)
Description Thomas Hennessy 2016-04-18 10:58:51 EDT 
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
Comment 2 Thomas Hennessy 2016-04-18 11:02 EDT 
Created attachment 1148232 [details]
sample evm.log lines showing how the display name become altered for ip address 10.2.2230.15
Comment 3 Thomas Hennessy 2016-04-18 11:07 EDT 
Created attachment 1148233 [details]
sample evm.log lines showing how the display name become altered for ip address 10.2.230.16
Comment 5 Thomas Hennessy 2016-04-21 15:47:06 EDT 
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
Comment 7 CFME Bot 2016-04-26 12:30:53 EDT 
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/40961a3cc401325b458d458b749b7a8b553e5d32

commit 40961a3cc401325b458d458b749b7a8b553e5d32
Author:     Adam Grare <agrare@redhat.com>
AuthorDate: Mon Apr 25 12:23:49 2016 -0400
Commit:     Adam Grare <agrare@redhat.com>
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(-)
Comment 10 errata-xmlrpc 2016-06-29 11:50:38 EDT 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.