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

    Refresh the XCP-ng + XOSTOR ISO ?

    Scheduled Pinned Locked Moved XOSTOR
    3 Posts 2 Posters 19 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.
    • S Offline
      shorian
      last edited by

      As per chat in https://xcp-ng.org/forum/post/100993 ; have had a failed update in one our of pools that necessitates using a local ISO to update XCP-ng , however as the pool is using XOSTOR one cannot use the standard release (in this instance xcp-ng-8.3.0-20250606.2.iso published on 18 Dec '25) and instead the update requires the XOSTOR packages to be in that latest iso.

      (Context: Due to the issue occurring during an update, we need an iso with the latest patch levels as the update has partially completed leaving the system with updated new packages. We can't use the older xostor friendly iso as there the linstor version is at 1.29.0 whilst the system now has linstor 1.29.2, and we can't use any other route (e.g network or cli) to update as these are not supported for xostor implementations.)

      The last xcp-ng iso with XOSTOR packages is xcp-ng-8.3.0-20250616-linstor-upgradeonly.iso which was released on 16 Jun '25. Is there a possibility of building an XOSTOR iso image each time we build a new xcp-ng iso so that the two are in sync (or even have a common iso)?

      And in the short term is there a way that I or someone cleverer could generate the iso?

      Appreciate any help; thank you!

      1 Reply Last reply Reply Quote 0
      • stormiS Offline
        stormi Vates 🪐 XCP-ng Team
        last edited by stormi

        So, I recently built a XOSTOR upgrade ISO for users what had had linstor packages from 8.2 linstor-testing repositories, version which was also 1.29.2.

        It might work for you.

        However, I offer no guarantees. Actually, I'm not even sure that using an upgrade is the right solution for your problem. A failed update (whatever that means here) is usually recoverable from command line.

        Here's the temporary link to the ISO image: https://repo.vates.tech/tmp/xcp-ng-8.3.0-20250616-linstor-upgradeonly.linstor-1-29-2.iso

        SHA256 Checksum: 8a488359f64e61310ee346d2bb635f69a8ea57c76c0ee5aa2df8c419a75c7f3a

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          shorian @stormi
          last edited by shorian

          @stormi You star, will let you know. Thank you!

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