Pool Restore Error Missing Column VM
-
I'm reinstalled xcp-ng on the same server, 8.3 beta. RE-install went fine, I was able to restore the XO-config. When I try to restore the Pool I get an error stating missing column VM. I'm new to xcp-ng and have never done a restore before. My understanding is it should overwrite the current pool.
If I try to restore one of the VM's it says wrong version.
Any idea why the pool won't restore? Pool backup was only a day old.
I'm using XOA self-compiled.metadataBackup.restore { "id": "4184667b-c483-458b-9e4f-0fde87da3e66/xo-pool-metadata-backups/5373c4ce-dd86-4bc6-8b91-5ce49963cf9d/35d05089-1b24-28b9-e9d8-4c718de20146/20240610T040000Z", "pool": "5f5aa3c1-a2ac-3d43-1aa9-09fd8fb0db0b" } { "code": "INTERNAL_ERROR", "params": [ "missing column", "VM", "pending_guidances_full" ], "url": "", "task": { "uuid": "07430e9b-2d88-b466-3461-1976f54ff5cc", "name_label": "[XO] Import pool metadata", "name_description": "", "allowed_operations": [], "current_operations": {}, "created": "20240611T22:32:43Z", "finished": "20240611T22:32:43Z", "status": "failure", "resident_on": "OpaqueRef:142fba18-8023-ed85-ae40-e608fec3975d", "progress": 1, "type": "<none/>", "result": "", "error_info": [ "INTERNAL_ERROR", "missing column", "VM", "pending_guidances_full" ], "other_config": {}, "subtask_of": "OpaqueRef:NULL", "subtasks": [], "backtrace": "(((process xapi)(filename ocaml/database/schema.ml)(line 108))((process xapi)(filename ocaml/database/db_xml.ml)(line 170))((process xapi)(filename list.ml)(line 121))((process xapi)(filename ocaml/database/db_xml.ml)(line 152))((process xapi)(filename ocaml/database/db_xml.ml)(line 215))((process xapi)(filename ocaml/database/db_xml.ml)(line 237))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 38))((process xapi)(filename ocaml/xapi/pool_db_backup.ml)(line 191))((process xapi)(filename ocaml/xapi/pool_db_backup.ml)(line 242))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 72)))" }, "message": "INTERNAL_ERROR(missing column, VM, pending_guidances_full)", "name": "XapiError", "stack": "XapiError: INTERNAL_ERROR(missing column, VM, pending_guidances_full) at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202406111131/packages/xen-api/_XapiError.mjs:16:12) at default (file:///opt/xo/xo-builds/xen-orchestra-202406111131/packages/xen-api/_getTaskResult.mjs:13:29) at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202406111131/packages/xen-api/index.mjs:1033:24) at file:///opt/xo/xo-builds/xen-orchestra-202406111131/packages/xen-api/index.mjs:1067:14 at Array.forEach (<anonymous>) at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202406111131/packages/xen-api/index.mjs:1057:12) at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202406111131/packages/xen-api/index.mjs:1230:14)" } -
Have you applied all of the patches to this new server? I suspect that you haven't, which will yield these types of issues.
-
@Danp Yes, all patches have been applied to the new XOA pool
-
@robs007 Hmmm... and host was rebooted after the patches were applied?

-
@Danp Sometimes the answer is so simple. I never rebooted after the patches were installed. Worked fine after that.
Thanks -
That's because the XAPI database format changed and only a XAPI restart or host restart would have reload XAPI and make it able to ingest the format you had a backup.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login