NSX Manager registration fails with NonUniqueResultException in VCF Automation 9.x

Products

• VCF Automation

Issue/Introduction

This article addresses registration failures for NSX Managers in VCF Automation 9.x. When the system poller attempts to validate the uniqueness of an NSX Manager hostname, the registration process fails with a NonUniqueResultException.

Environment

VCF Automation 9.x

Cause

A defect exists in HibernateNSXTManagerDao.java regarding hostname validation logic. The code utilizes an ILIKE SQL query with MatchMode.ANYWHERE, which triggers an incorrect match when one FQDN is a substring of another (e.g., example.com.####.biz incorrectly matches test-example.com.####.biz). When multiple rows are returned, Hibernate throws an exception as it expects a unique result.

Resolution

Fix scheduled for a future release. Until the fix is available, apply the following workarounds:

1. Registration Order: Attempt to register the NSX Manager with the shorter hostname first, followed by the one with the longer FQDN prefix.
2. Hostname Review: Ensure that newly added NSX domain names are not substrings of already registered NSX domains.

Additional Information

For defects and enhancements only: recommend the user subscribe to this KB to be updated on fix status.