Problem description
Nutanix AHV VM discovery was failing for the new deployment/setup with Internal Error 500. CURL API commands to list VMs from the Druva Backup Proxy were also failing with an Internal Error [Error code: 500].
Cause
Virtual machines (VMs) were migrated from VMware ESXi to Nutanix AHV. There were stale NIC entries left over from the migration process. These stale NIC entries caused issues while discovering the VMs, and we were getting authentication and internal server errors when the Druva Backup Proxy attempted to discover VMs or via API calls.
Traceback
main_service.log
level=error ts=2025-09-07T14:48:03.679774473+08:00 filename=discovery.go:371 message="Sync discovery command request failed when fetching vms." Layer=Discovery
level=error ts=2025-09-07T14:48:03.679912269+08:00 stack="Nutanix AHV Server could not complete your Request\\ngoroutine 307"
CURL API command and error:
Command:
curl-XPOST-u'USER_NAME:PASSWORD'-H'Content-Type: application/json'--insecure-d'{ "kind": "vm", "offset": 0, "length": 50 }'
Error:
{
"message": {
"api_version": "3.1",
"code": 500,
"message_list": [
{
"message": "Internal Server Error. '<' not supported between instances of 'NoneType' and 'int'",
"reason": "INTERNAL_ERROR"
}
],
"state": "ERROR"
}
}
Resolution
Involve Nutanix support and inform the situation, ask for Python utility to identify and clean up stale NIC entries on the affected CVM.
The utility was downloaded from: “https://download.nutanix.com/kbattachments/17527/nic_idf_delete_utility.py”
Note: Consult with the Nutanix Support Team before performing the detection and cleanup.
Verification
After the cleanup, run the Curl command again from the backup Proxy to confirm.
curl -X POST -u 'USERNAME:PASSWORD' -H 'Content-Type: application/json' --insecure -d '{ "kind": "vm", "offset": 0, "length": 50 }'Trigger the VM discovery from Druva Console.