Error: Expected "actual" to be strictly unequal to: false

Gheppy

I updated to the latest version of today and I have the following error on delta backup
Error: Expected "actual" to be strictly unequal to: false

Gheppy

the error disappeared with commit efc3f45ef63e4ee7bb5efeca063328faafade9bb

thank you

Darkbeldin

I bit more info would be nice.

What have you updated?
What version off XCP-ng are you using?
What version of Xo are you using?
Can you paste the log file error so we can go further?

Gheppy

iIt also happens on full backup to

XCP-NG is up to date and is 8.2
I use XOCE form github commit 27aa10ef4be26b913c76f1157bcbcac1605f400c5

{
  "data": {
    "mode": "full",
    "reportWhen": "always"
  },
  "id": "1618929334586",
  "jobId": "badbe548-710d-4822-b72e-570d00c3120f",
  "jobName": "XOCE01",
  "message": "backup",
  "scheduleId": "142e1934-9397-4020-9f66-792a391694a8",
  "start": 1618929334586,
  "status": "failure",
  "infos": [
    {
      "data": {
        "vms": [
          "08018514-2ee1-a849-783d-d79c4321f759"
        ]
      },
      "message": "vms"
    }
  ],
  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "08018514-2ee1-a849-783d-d79c4321f759"
      },
      "id": "1618929335155",
      "message": "backup VM",
      "start": 1618929335155,
      "status": "failure",
      "end": 1618929335564,
      "result": {
        "generatedMessage": true,
        "code": "ERR_ASSERTION",
        "actual": false,
        "expected": false,
        "operator": "notStrictEqual",
        "message": "Expected \"actual\" to be strictly unequal to: false",
        "name": "AssertionError",
        "stack": "AssertionError [ERR_ASSERTION]: Expected \"actual\" to be strictly unequal to: false\n    at VmBackup._snapshot (/opt/xen-orchestra/@xen-orchestra/backups/_VmBackup.js:118:12)\n    at VmBackup.run (/opt/xen-orchestra/@xen-orchestra/backups/_VmBackup.js:344:18)\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)"
      }
    }
  ],
  "end": 1618929335564
}

Gheppy

the error disappeared with commit efc3f45ef63e4ee7bb5efeca063328faafade9bb

thank you

olivierlambert

This can happen from time to time on master (despite we do every "broken" code in dedicated branches), sometimes you can have a surprise.

That's why it's important, before anything, to get the latest commit and rebuild, to see if the issue persist. If it's the case, then reporting the problem will be helpful