285 views

Description

When an ESX Server is migrated to a different vCenter, a new record is created with a relationship to the new vCenter, but a record with a relationship to the original vCenter still remains. 

Steps to Reproduce

 

  1. Discover vCenter.
  2. Notice that a relationship is created between the ESX Server and vCenter.
  3. Migrate the ESX Server to a different vCenter (new).
  4. Discover the vCenter that contains the migrated ESX server.
Expected result:  The ESX Server record created in step 1 now shows a relationship to the new vCenter.
Actual result: An ESX server record is created that has a relationship to the new vCenter. However, the record with the relationship to the original vCenter still exists.

Workaround

To avoid creating duplicate records during an ESX server migration, upgrade to a version that contains the fix:

  • Jakarta Patch 8
  • Kingston Patch 2
  • London

If you have already experienced this issue, you must remove the duplicate record manually.


Related Problem: PRB1241320

Seen In

There is no data to report.

Intended Fix Version

London

Fixed In

Jakarta Patch 8
Kingston Patch 2

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-06-06 14:56:35
Published:2018-01-17