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

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    616 Posts 53 Posters 379.1k Views 73 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.
    • rzrR Offline
      rzr Vates 🪐 XCP-ng Team
      last edited by rzr

      XCP-ng 8.3 LTS Updated installer ISO

      The installer ISO has been refreshed with up date packages already published.

      The image can be downloaded from:

      https://repo.vates.tech/tmp/xcp-ng-8.3.0-20260709.testing.iso

      The procedure to install XCP-ng 8.3 remains the same.

      The refreshed installer ships updated Xen, Linux kernel and some drivers/firmware, which help with deploying XCP-ng 8.3 on hardware that needs changes introduced by updates not present in previous ISO image releases.

      This refreshed ISO has been validated on a subset of supported hardware. Additional testing on any hardware from the community would be greatly appreciated.

      As with previous installer releases, it can be used to upgrade XCP-ng from a previous major release (8.0, 8.1 or 8.2). Refer to the Upgrade documentation. For existing XCP-ng 8.3 installations, there’s no need to use this ISO image. Regular yum updates achieve the same results as a fresh installation with that ISO image.

      Installer improvements include minor enhancements related to software RAID1 support for the system disks, including support for more than 2 disks in the RAID1 array if anyone really wants that.

      New maintenance update candidates for XCP-ng 8.3 LTS

      This release batch includes a VBD leak regression fix in XAPI and minor changes needed to build the installer ISO.

      A regression was introduced to the VM.revert operation in xapi-26.1.4-3.3, which left VBDs attached to the VM when they are not present in the reverted-to snapshot (instead of destroying such VBDs, as was done before).

      VMs that were reverted to their snapshots after xapi-26.1.4-3.3 may have such "leftover" VBDs. Advanced users can use the leaked_vbds script to detect possible cases in your pools. Sadly, there is no way to automatically distinguish a VBD that was created after a VM.revert from a VBD that survived the VM.revert, so this script relies on the user to determine if the suspicious VBDs are indeed affected or not.

      What changed

      Control Plane

      • xapi: Fix non-snapshotted VBDs staying attached after VM.revert

      Versions

      • xapi: 26.1.11-1.2.xcpng8.3 -> 26.1.11-1.3.xcpng8.3
      • xcp-ng-release: 8.3.0-37 -> 8.3.0-38

      Test on XCP-ng 8.3

      yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates
yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates
reboot

      The usual update rules apply: pool coordinator first, etc.

      What to test

      As usual, normal use and anything else you want to test.

      Test window before official release of the updates

      ~5 days

      We would like to thank users who shared feedback since our last call for testing: @Andrew, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro , @marcoi.

      acebmxerA F 2 Replies Last reply Reply Quote 1
      • acebmxerA Offline
        acebmxer @rzr
        last edited by acebmxer

        @rzr

        Just tried to apply update. Unable to put master host into maintenance mode - not enough memory...

        https://xcp-ng.org/forum/post/106814

        Edit - Updated both host after manually migrating the vms. Also noticed when i thought i was updating the master host first it might not have been.

        With Twinstore installed and enabled HA was also enabled. After first host came back on line i looked at the pool advanced settings and saw host 2 was master not host 1.

        Both host have been updated and rebooted. @olivierlambert would this change post master from one host to the other? XO did loose access to the VMs while the first host rebooted. So i am alittle confused...

        Once host 2 came back online pool master is switched back to host 1 again...

        will look for any other odd things.

        1 Reply Last reply Reply Quote 1
        • F Offline
          flakpyro @rzr
          last edited by

          @rzr

          Is there something specific needed for the leaked_vbds script?

          When i run it i get:

          [09:37 xcpng-prd-01 ~]# ./leaked_vbds 
Traceback (most recent call last):
  File "./leaked_vbds", line 23, in <module>
    snap = xapi.VM.get_parent(snap)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request
    result = _parse_result(getattr(self, methodname)(*full_params))
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result
    raise Failure(result['ErrorDescription'])
XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:29']
          A 1 Reply Last reply Reply Quote 0
          • A Offline
            andriy.sultanov Vates 🪐 XAPI & Network Team @flakpyro
            last edited by andriy.sultanov

            @flakpyro I'll add some additional error-checking, but looks like you're affected by the snapshot_of issue and should run another script (yes, I know...) to fix these stale references: https://github.com/xcp-ng/xcp/blob/master/scripts/snapshot-fixer.py

            F A 2 Replies Last reply Reply Quote 2
            • F Offline
              flakpyro @andriy.sultanov
              last edited by

              @andriy.sultanov

              Thanks

              I ran that second script on the master and it did indeed find entries:

              ./snapshot-fixer.py rewrite
INFO:root:Check HA...
INFO:root:Shutting down xapi...
INFO:root:Regenerating database...
INFO:root:The VM d6befe36-fea7-04f3-25f1-feada684702b has Ref:9 as its "snapshot_of" value, changing to null.
INFO:root:The VM e013d9ed-63b1-9c9f-a228-d48a6047688c has Ref:89 as its "snapshot_of" value, changing to null.
INFO:root:The VM 060df7ee-8af4-4c93-8265-bfa3024ccacd has Ref:1 as its "snapshot_of" value, changing to null.
INFO:root:The VM da7b6ff6-d722-2120-7cc4-a1e0038a216e has Ref:307 as its "snapshot_of" value, changing to null.
INFO:root:The VM 4178b057-efee-427e-bcad-67323419ac7a has Ref:9 as its "snapshot_of" value, changing to null.
INFO:root:The VM 8d624e49-ca99-4af6-b17c-38cad0646194 has Ref:1 as its "snapshot_of" value, changing to null.
INFO:root:The VM dc72da43-f144-3343-5ee5-a0dbffd209f6 has Ref:251 as its "snapshot_of" value, changing to null.
INFO:root:The VM e8c6376b-49e1-422b-551a-35420f70af2a has Ref:8 as its "snapshot_of" value, changing to null.
INFO:root:The VM 25eb14ab-e943-0d18-2137-c681e1191346 has Ref:11 as its "snapshot_of" value, changing to null.
INFO:root:The VM 6f819166-b008-4a03-a692-fcbd75018be9 has Ref:1 as its "snapshot_of" value, changing to null.
INFO:root:The VM 9d1a57e8-3531-4b55-9682-f775215866df has Ref:1 as its "snapshot_of" value, changing to null.
INFO:root:The VM 0ac88f7c-d79b-281e-cf1f-a2392ba594ed has Ref:29 as its "snapshot_of" value, changing to null.
INFO:root:The VM 1f3541c4-8c81-4959-9cbe-edbec9481220 has Ref:1 as its "snapshot_of" value, changing to null.
INFO:root:Writing database to /var/lib/xcp/state.db
INFO:root:Starting up xapi...

              after which it shows clean now:

              ./snapshot-fixer.py dry-run
INFO:root:Regenerating database...

              However i am still getting the same error when trying to run leaked_vbs:

              ./leaked_vbds 
Traceback (most recent call last):
  File "./leaked_vbds", line 23, in <module>
    snap = xapi.VM.get_parent(snap)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request
    result = _parse_result(getattr(self, methodname)(*full_params))
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result
    raise Failure(result['ErrorDescription'])
XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:29']
              1 Reply Last reply Reply Quote 1
              • A Offline
                Andrew Top contributor @andriy.sultanov
                last edited by

                @rzr Updates installed and running. I also run the snapshot-fixer.py and xapi_leaked_vbds.py scripts... The fixer found/fixed lots on many pools...

                @andriy.sultanov I have the same error... On one pool, I ran snapshot-fixer.py and it fixed about 50 of them, but xapi_leaked_vbds.py still returns an error (before and after fix):

                Traceback (most recent call last):
  File "./xapi_leaked_vbds.py", line 23, in <module>
    snap = xapi.VM.get_parent(snap)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request
    result = _parse_result(getattr(self, methodname)(*full_params))
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result
    raise Failure(result['ErrorDescription'])
XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:119']
                A 1 Reply Last reply Reply Quote 0
                • A Offline
                  andriy.sultanov Vates 🪐 XAPI & Network Team @Andrew
                  last edited by

                  @Andrew @flakpyro I've updated the script, could you try running it again?

                  https://gist.github.com/last-genius/edf7dab3b1847ec5bb1d9917996eba41

                  A F 2 Replies Last reply Reply Quote 0
                  • A Offline
                    Andrew Top contributor @andriy.sultanov
                    last edited by

                    @andriy.sultanov No error... returns nothing.

                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      andriy.sultanov Vates 🪐 XAPI & Network Team @Andrew
                      last edited by

                      @Andrew That means you likely don't have any "leaked" VBDs 🙂

                      1 Reply Last reply Reply Quote 0
                      • F Offline
                        flakpyro @andriy.sultanov
                        last edited by

                        @andriy.sultanov

                        Running it now shows no error! And no output so looks like i have no issues!

                        1 Reply Last reply Reply Quote 0

                        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
                        • First post
                          Last post