Continuous Replication 5.9 fail to delete VDI from VM XO_DELTA_EXPORT
sorry... (copy and paste error...)
I redo all but from the "git checkout" command I receive a warning...
root@ubuntu:/opt/xo-server# git pull remote: Counting objects: 150, done. remote: Compressing objects: 100% (58/58), done. remote: Total 150 (delta 101), reused 127 (delta 92), pack-reused 0 Ricezione degli oggetti: 100% (150/150), 119.97 KiB | 0 bytes/s, done. Risoluzione dei delta: 100% (101/101), completed with 32 local objects. Da https://github.com/vatesfr/xo-server 2d39a1a..dc9af66 backupRestoration -> origin/backupRestoration edbeb55..eac4178 cbs-exposeVmAppliance -> origin/cbs-exposeVmAppliance * [nuovo branch] fix-export-import -> origin/fix-export-import * [nuovo branch] fixCreateVm-resourceSet -> origin/fixCreateVm-resourceSet de7672b..ff16533 next-release -> origin/next-release f217c84..9ac1545 nr-xosan2 -> origin/nr-xosan2 Already up-to-date. root@ubuntu:/opt/xo-server# root@ubuntu:/opt/xo-server# git branch -a * stable remotes/origin/HEAD -> origin/next-release remotes/origin/architecture-rework remotes/origin/babel-config remotes/origin/backup-cleanup remotes/origin/backupRestoration remotes/origin/cancelable-backups remotes/origin/cancellable-vm-import remotes/origin/cbs-exposeVmAppliance remotes/origin/collection-patch remotes/origin/disable-quiesce-fallback remotes/origin/extract-xo-fs-to-module remotes/origin/fix-export-import remotes/origin/fix-registerUser remotes/origin/fixCreateVm-resourceSet remotes/origin/fixResourceSet remotes/origin/force-ext4 remotes/origin/jobTimezone remotes/origin/master remotes/origin/next-release remotes/origin/nr-try-fix-xosan-beta remotes/origin/nr-update-noVNC remotes/origin/nr-xosan remotes/origin/nr-xosan2 remotes/origin/olt-detectUnheathlyChain remotes/origin/olt-testsrstats remotes/origin/patch remotes/origin/revert-CR-DR-job remotes/origin/stable remotes/origin/utils remotes/origin/why-is-node-running root@ubuntu:/opt/xo-server# git checkout fix-export-import error: Your local changes to the following files would be overwritten by checkout: package.json Please commit your changes or stash them before you switch branches. Aborting root@ubuntu:/opt/xo-server#
Well your git is not doing this automatically, that's why it's hard to support non-XOA installs ^^
So do a:
git checkout origin/fix-export-import
root@ubuntu:/opt/xo-server# git checkout origin/fix-export-import error: Your local changes to the following files would be overwritten by checkout: package.json Please commit your changes or stash them before you switch branches. Aborting root@ubuntu:/opt/xo-server#
Danp last edited by
You'll need to stash your changes before you can switch branches --
git stash -u
No, not the same message. Please stash your changes first.
Damn you @Danp
root@ubuntu:/opt/xo-server# git checkout origin/fix-export-import
Note: checking out 'origin/fix-export-import'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
HEAD si trova ora a 9b25da4... chore(Xapi#importDeltaVm): use asyncMap
Does't matter that's fine, you are in the right commit.
yarnand start again
ok now I try:
yarn install --force??
yarnalone should be fine
root@ubuntu:/opt/xo-server# yarn yarn install v0.24.6 [1/4] Resolving packages... [2/4] Fetching packages... warning email@example.com: The platform "linux" is incompatible with this module. info "firstname.lastname@example.org" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... [4/4] Building fresh packages... success Saved lockfile. $ npm run build > email@example.com prebuild /opt/xo-server > index-modules src/api src/xapi/mixins src/xo-mixins index generated src/xapi/mixins/index.js index generated src/api/index.js index generated src/xo-mixins/index.js > firstname.lastname@example.org build /opt/xo-server > gulp build --production [19:03:27] Using gulpfile /opt/xo-server/gulpfile.js [19:03:27] Starting 'build'... [19:03:27] Starting 'clean'... [19:03:28] Finished 'clean' after 110 ms [19:03:28] Starting 'buildCoffee'... [19:03:28] Starting 'buildEs6'... [19:03:33] Finished 'buildCoffee' after 5.79 s [19:03:47] Finished 'buildEs6' after 20 s [19:03:47] Finished 'build' after 20 s Done in 55.87s. root@ubuntu:/opt/xo-server#
ok... now i restart all and I try to do some test...
I will inform you here.
Thanks for the support (and the patience)
Build is fine, indeed now just let me know about the tests
I did some tests, the situation got worse.
Now, even the first execution of the replica is not successfully completed.
In the Task section, the job is completed (100%) and disappears.
In the Logs table in the backup section, the job is not marked as finished (remain marked "Started" in yellow).
In the Setting>Logs section: "No logs so far".
On the replica receiving machine, the VM appears with the suffix [Importing ...]
Hi Oliver, I did some tests again after applying the lastest fix.
Now the job arrives at the end and is marked as "finished" (green) in the backup log.
The replicated VM on the target XEN (replica) are renamed correctly.
But... the initial problem remains.
XO can not delete snapshots created for replication, which become zombies.
Basically ... we're back to the beginning.
You can keep on the GitHub issue to tell us the result, it's better to follow
fulvio last edited by fulvio
This post is deleted!
When you start an issue somewhere, please continue the discussion there