XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Unable to unblock a vm for reversion of snapshot

    Scheduled Pinned Locked Moved XCP-ng
    7 Posts 3 Posters 511 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      dsiminiuk
      last edited by dsiminiuk

      I am using a pre-built xo VM running on my pool master created from a script by Ronivay and it has been working well. I had the VM set to prevent accidental deletion and shutdown and with autostart. No problem.

      I took a snapshot of it and upgraded the kernel to hwe (6.x) and upon reboot it never came back up on the network.

      I tried to revert to the snapshot via xe...

      xe snapshot-revert snapshot-uuid=1a91d725-65b0-7bb7-f70f-0be5903e8d44
      You attempted an operation that was explicitly blocked (see the blocked_operations field of the given object).
      ref: e8d5def9-e079-d7a6-e106-fe8d96f55cac (xo-ce)
      code: false
      

      And so I attempted to set all the blocked-operations vm-parameters to false, and I got all of them except one.

      xe vm-param-list uuid=e8d5def9-e079-d7a6-e106-fe8d96f55cac | fgrep blocked
      
      blocked-operations (MRW): destroy: false; pause: false; clean_reboot: false; suspend: false; hard_reboot: false; hard_shutdown: false; clean_shutdown: false; (unknown operation): true
      

      I can't revert to the snapshot and I am still unable to set the "(unknown operation)" parameter to false.

      I have a backup of the XO-Config so i could start over but it would be nice to not have to do that.

      Any pointers would be most welcome.

      Thanks
      Danny

      1 Reply Last reply Reply Quote 0
      • D Offline
        dsiminiuk
        last edited by

        I figured out another way around it. I imported a new xo VM with the same script and connected it to my pool master just long enough to revert to the snapshot of the XO I wanted to keep.
        I was able to login and delete the temporary XO VM.
        I would still like to understand what the
        blocked-operations (MRW): (unknown operation): true;
        means.

        Anyway, not urgent.
        Thanks
        Danny

        D 1 Reply Last reply Reply Quote 0
        • D Offline
          dsiminiuk @dsiminiuk
          last edited by

          Additional observations...

          When a VM is set to prevent accidental deletion (only)...

          blocked-operations (MRW): destroy: true
          

          When set to prevent accidental shutdown (only)...

          blocked-operations (MRW): clean_shutdown: true; (unknown operation): true; pause: true; hard_reboot: true; suspend: true; hard_shutdown: true; clean_reboot: true
          

          And of course with both options enabled, it is the aggregation of both sets.

          blocked-operations (MRW): destroy: true; clean_shutdown: true; (unknown operation): true; pause: true; hard_reboot: true; suspend: true; hard_shutdown: true; clean_reboot: true
          

          Danny

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            The unknown operation thing is weird. Pinging @MathieuRA if we can reproduce.

            DanpD 1 Reply Last reply Reply Quote 0
            • DanpD Offline
              Danp Pro Support Team @olivierlambert
              last edited by

              @olivierlambert See prior discussion here

              D 1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                I'm not sure, are we still affected? Should it be fixed in XO?

                1 Reply Last reply Reply Quote 0
                • D Offline
                  dsiminiuk @Danp
                  last edited by

                  @Danp I tried some of the xe commands listed in that post like xe vm-param-clear and xe vm-param-remove and wasn't successful.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post