Importing vm from VMware ESXi fails
-
Hello,
I am trying to import a stopped virtual machine from an ESXi server, but the import process is not actually running and I immediately get this error:sr.getVdiChainsInfo { "sr": "41cd87bf-bcdd-e344-3c6e-f4b6ecb62c74" } { "message": "Cannot read properties of undefined (reading 'managed')", "name": "TypeError", "stack": "TypeError: Cannot read properties of undefined (reading 'managed') at file:///opt/xo/xo-builds/xen-orchestra-202403160756/packages/xo-server/src/xapi/mixins/storage.mjs:84:15 at arrayEach (/opt/xo/xo-builds/xen-orchestra-202403160756/node_modules/lodash/_arrayEach.js:15:9) at forEach (/opt/xo/xo-builds/xen-orchestra-202403160756/node_modules/lodash/forEach.js:38:10) at Xapi.getVdiChainsInfo (file:///opt/xo/xo-builds/xen-orchestra-202403160756/packages/xo-server/src/xapi/mixins/storage.mjs:83:5) at Xo.apply (file:///opt/xo/xo-builds/xen-orchestra-202403160756/packages/xo-server/src/api/sr.mjs:941:27) at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202403160756/packages/xo-server/src/xo-mixins/api.mjs:238:25) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202403160756/packages/xo-server/src/xo-mixins/api.mjs:366:33)" }
best regards,
Abu -
Solved by 583c728
-
Workaround: Rolling back to...
seems to solve the problem:
-
So unfortunately, today's early commits don't fix the problem...
sr.getAllUnhealthyVdiChainsLength {} { "message": "Cannot read properties of undefined (reading 'managed')", "name": "TypeError", "stack": "TypeError: Cannot read properties of undefined (reading 'managed') at file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/xapi/mixins/storage.mjs:84:15 at arrayEach (/opt/xo/xo-builds/xen-orchestra-202403181050/node_modules/lodash/_arrayEach.js:15:9) at forEach (/opt/xo/xo-builds/xen-orchestra-202403181050/node_modules/lodash/forEach.js:38:10) at Xapi.getVdiChainsInfo (file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/xapi/mixins/storage.mjs:83:5) at forEach (file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/api/sr.mjs:928:60) at Array.forEach (<anonymous>) at Xo.apply (file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/api/sr.mjs:927:100) at file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/_pDebounceWithKey.mjs:45:22 at Promise._execute (/opt/xo/xo-builds/xen-orchestra-202403181050/node_modules/bluebird/js/release/debuggability.js:384:9) at Promise._resolveFromExecutor (/opt/xo/xo-builds/xen-orchestra-202403181050/node_modules/bluebird/js/release/promise.js:518:18) at new Promise (/opt/xo/xo-builds/xen-orchestra-202403181050/node_modules/bluebird/js/release/promise.js:103:10) at Xo.apply (file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/_pDebounceWithKey.mjs:44:20) at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/xo-mixins/api.mjs:238:25) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202403181050/packages/xo-server/src/xo-mixins/api.mjs:366:33)" }
-
So rolling back for sure solved the issue and then the import went fine?
I haven't imported from ESXi recently but it always was a smooth process when I used it previously.
-
@planedrop Yes, commit c6451imports seamlessly
-
@abudef Odd, I'll see if I can do some testing with this in my lab with the latest commit, no promises though, quite a busy week for me.
-
-
Solved by 583c728
-
-