NetApp Shift Discovery Error EDSCGMTP002

James3

We have been using NetApp Shift to convert our VMs from VMware to Hyper-V.  I am now starting on our second group of hosts running through a different vcenter server.  And it will not do a discovery of that cluster.  It will discover the VMs, then fail on Discovering volumes and mapping to VMs.

We have a primary and a disaster recovery cluster both with their own vcenter, it fails to discover either.  They are using Zerto to replicate between the two.

I am wondering if it is because that cluster is running Zerto replication.  Is Shift and Zerto compatible?

EDSCGMTP002: Mount paths are empty while getting volumes for mountpaths for site - undefined

[
  [
    {
      "uid": "f6d211d8-3b79-4992-be93-036a2781e930",
      "code": "ECRUAFAC002",
      "message": "ECRUAFAC002: The server returned HTTP status 500 while performing \"POST\" on endpoint - \"https://10.230.64.128:3700/api/setup/volume/discovery?siteId=3a59d1a2-7930-4b99-871d-d85890ef356e&virtEnvId=1d79524f-8dab-4fa2-8aae-9a77f85c386b\"; Error code: \"ERR_BAD_RESPONSE\"; Error message: \"Check error chain\"",
      "level": "error",
      "endPoint": "",
      "stack": "SystemError: ECRUAFAC002: The server returned HTTP status 500 while performing \"POST\" on endpoint - \"https://10.230.64.128:3700/api/setup/volume/discovery?siteId=3a59d1a2-7930-4b99-871d-d85890ef356e&virtEnvId=1d79524f-8dab-4fa2-8aae-9a77f85c386b\"; Error code: \"ERR_BAD_RESPONSE\"; Error message: \"Check error chain\"\n    at catchErr (C:\\snapshot\\draas\\core\\lib\\stepWorker\\utils\\axiosf.js)\n    at Object.post (C:\\snapshot\\draas\\core\\lib\\stepWorker\\utils\\axiosf.js)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async invokeSvc (C:\\snapshot\\draas\\core\\lib\\stepWorker\\ext\\stepTypes\\rest.js)\n    at async Object.execute (C:\\snapshot\\draas\\core\\lib\\stepWorker\\ext\\stepTypes\\rest.js)\n    at async executeStep (C:\\snapshot\\draas\\core\\lib\\stepWorker\\stepWorker.js)"
    },
    {
      "uid": "1bc06a49-f85f-454d-b8f3-9cc94217e8a1",
      "code": "ECRUAFAC002",
      "message": "ECRUAFAC002: The server returned HTTP status 500 while performing \"POST\" on endpoint - \"https://10.230.64.128:3701/api/discovery/site/3a59d1a2-7930-4b99-871d-d85890ef356e/volume/search\"; Error code: \"ERR_BAD_RESPONSE\"; Error message: \"Check error chain\"",
      "level": "error",
      "endPoint": "/volume/discovery?siteId=3a59d1a2-7930-4b99-871d-d85890ef356e&virtEnvId=1d79524f-8dab-4fa2-8aae-9a77f85c386b",
      "stack": "SystemError: ECRUAFAC002: The server returned HTTP status 500 while performing \"POST\" on endpoint - \"https://10.230.64.128:3701/api/discovery/site/3a59d1a2-7930-4b99-871d-d85890ef356e/volume/search\"; Error code: \"ERR_BAD_RESPONSE\"; Error message: \"Check error chain\"\n    at catchErr (C:\\snapshot\\draas\\draas\\draas-setup\\utils\\axiosf.js)\n    at Object.post (C:\\snapshot\\draas\\draas\\draas-setup\\utils\\axiosf.js)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Object.execute (C:\\snapshot\\draas\\draas\\draas-setup\\adapters\\discovery\\discoverVolumes.js)\n    at async execute (C:\\snapshot\\draas\\draas\\draas-setup\\actions\\discoverVolumes.js)\n    at async Object.execute (C:\\snapshot\\draas\\draas\\draas-setup\\controllers\\mapVolumesToVMsController.js)\n    at async Object.fn (C:\\snapshot\\draas\\draas\\draas-setup\\utils\\routerUtils.js)\n    at async Object.executeController (C:\\snapshot\\draas\\draas\\draas-setup\\utils\\routerUtils.js)"
    },
    {
      "uid": "36326c7c-d10b-4216-a217-f436c1bfa502",
      "code": "EDSCGMTP002",
      "message": "EDSCGMTP002: Mount paths are empty while getting volumes for mountpaths for site - undefined",
      "level": "error",
      "endPoint": "/site/3a59d1a2-7930-4b99-871d-d85890ef356e/volume/search",
      "stack": "ApplicationError: EDSCGMTP002: Mount paths are empty while getting volumes for mountpaths for site - undefined\n    at validateInput (C:\\snapshot\\draas\\draas\\draas-discovery\\controllers\\getVolumesForMountPathsController.js)\n    at Object.execute (C:\\snapshot\\draas\\draas\\draas-discovery\\controllers\\getVolumesForMountPathsController.js)\n    at Object.fn (C:\\snapshot\\draas\\draas\\draas-discovery\\utils\\routerUtils.js)\n    at Object.executeController (C:\\snapshot\\draas\\draas\\draas-discovery\\utils\\routerUtils.js)\n    at C:\\snapshot\\draas\\draas\\draas-discovery\\routers\\discoveryRouter.js\n    at Layer.handle [as handle_request] (C:\\snapshot\\draas\\draas\\draas-discovery\\node_modules\\express\\lib\\router\\layer.js:95:5)\n    at next (C:\\snapshot\\draas\\draas\\draas-discovery\\node_modules\\express\\lib\\router\\route.js:144:13)\n    at Route.dispatch (C:\\snapshot\\draas\\draas\\draas-discovery\\node_modules\\express\\lib\\router\\route.js:114:3)\n    at Layer.handle [as handle_request] (C:\\snapshot\\draas\\draas\\draas-discovery\\node_modules\\express\\lib\\router\\layer.js:95:5)\n    at C:\\snapshot\\draas\\draas\\draas-discovery\\node_modules\\express\\lib\\router\\index.js:284:15"
    }
  ]
]

James3

NetApp email support came through for me.  Apparently the discovery process requires at least one VM to be on the NFS shift datastore or the discovery fails with the above error.