Notifications

665 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.

Fixed In

Jakarta Patch 8
Kingston Patch 2
London

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-08-14 05:24:58
Published:2018-01-17