Continuous Replication 5.9 fail to delete VDI from VM XO_DELTA_EXPORT



  • What snapshots exist after the job finishes? Are there more than one per VM?

    You may want to post your issue to their official issues list over on Github -- https://github.com/vatesfr/xo-web/issues/new



  • @Danp at the end of the job only the last new snapshot remain, and only one for each VM (the last)

    In the storage repo we can see some vdi zombie.

    0_1498048426403_28be12ad-411d-4952-81a5-fbe9cc1bf2bd-image.png

    0_1498048657006_36c4b871-b8c6-4f37-95ef-0f67fdd5aa64-image.png



  • Are you able to manually remove these remnant VDIs?

    Are they listed in the "Orphaned snapshot VDIs" under Dashboard > Health?

    I see you opened an issue on GH. Hopefully one of the devs will chime in soon.



  • @Danp Yes, from Xencenter I can delete them.
    No orphaned listed inside Health section.

    Meanwhile I continue to use v5.6.4 that works fine 🙂



  • @fulvio can you follow instructions on the issue? I think we fixed that 🙂 https://github.com/vatesfr/xo-web/issues/2227



  • @olivierlambert @Danp I'm sorry Olivier, but I don't know which are the right steps to apply this patch (I dont know GitHub very well)



  • You need to go into the xo-server folder and switch to the right branch (git checkout fix-export-import then yarn)



  • @olivierlambert ok... i'm gonna try. Thanks.



  • @olivierlambert

    root@ubuntu:/opt/xo-server# git checkout fix-export-import
    error: pathspec 'fix-export-import' did not match any file(s) known to git.



  • git pull first to get the latest data from the remote, then git checkout the branch.



  • @olivierlambert

    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 checkout fix-export-import
    -bash: root@ubuntu:/opt/xo-server#: File o directory non esistente
    


  • @olivierlambert

    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



  • @olivierlambert

    same message:

    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#


  • 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
    root@ubuntu:/opt/xo-server#



  • Does't matter that's fine, you are in the right commit. yarn and start again xo-server



  • @olivierlambert

    ok now I try: yarn install --force ??


Log in to reply