HI

Hypervisor version?
8.2 build 2022-02-11
Are you running XOA or XO from sources?
-- If XO, which commit?
Im using XOA for import vm
Specifics about the VM being imported
Windows 2008 VM
-- OVA or XVA?
OVA
-- Did you download it? If so, link?
Im migrating a vmware to XCP-NG

Note: I migrated several vms in this scenario and only this one is giving this error

Hi, im getting this error importing a vm:

I have no idea how to solve this, i imported many vms.

HTTP handler of vm.import
undefined
{
  "code": "DEVICE_ALREADY_EXISTS",
  "params": [
    "0"
  ],
  "call": {
    "method": "VBD.create",
    "params": [
      {
        "bootable": false,
        "empty": false,
        "mode": "RW",
        "other_config": {},
        "qos_algorithm_params": {},
        "qos_algorithm_type": "",
        "type": "Disk",
        "unpluggable": false,
        "userdevice": "0",
        "VDI": "OpaqueRef:ceab1a5c-ff9d-4bb1-a053-749662448aae",
        "VM": "OpaqueRef:e7ce99ab-23ce-4f60-86f1-ee60e855d980"
      }
    ]
  },
  "message": "DEVICE_ALREADY_EXISTS(0)",
  "name": "XapiError",
  "stack": "XapiError: DEVICE_ALREADY_EXISTS(0)
    at Function.wrap (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/_XapiError.js:16:12)
    at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/transports/json-rpc.js:41:27
    at AsyncResource.runInAsyncScope (node:async_hooks:199:9)
    at cb (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:464:21)
    at process.topLevelDomainCallback (node:domain:152:15)
    at process.callbackTrampoline (node:internal/async_hooks:128:24)"
}

@stormi Hi, its good to know.

Thanks for the answer i think now its solved and explained.

@ronivay said in Update and passwd:

It's quite normal that any new package that adds a service user modifies passwd file or some patch could've added/modified such user. Check the passwd backup file located in /etc/passwd- if its modification time matches the time you ran updates. If yes, then you can just diff passwd and passwd- to see what was actually changed.

# diff passwd passwd-
28d27


< tss:x:59:59:Account used by the trousers package to sandbox the tcsd daemon:/dev/null:/sbin/nologin

Hello, thanks everyone for the answer.
I will do this steps.

Hi, i have Zabbix monitoring passwd file and after applying patches i got a warn this file has been modified for all hypervisors hosts.

Hello, i have applied 80 patchs and one of then changed the passwd file.
I need to know exactly what user/password this patch changed.