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

    XOSTOR hyperconvergence preview

    Scheduled Pinned Locked Moved
    XOSTOR
    45
    443
    77.4k
    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.
    • stormiS
      stormi Vates 🪐 XCP-ng Team @Jonathon
      last edited by

      @Jonathon Never use --skip-broken.

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

        @Jonathon What's the output of yum repolist?

        J 1 Reply Last reply Reply Quote 0
        • J
          Jonathon @stormi
          last edited by

          @stormi said in XOSTOR hyperconvergence preview:

          yum repolist

          lol glad I checked then

          # yum repolist
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-linstor: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
repo id                                                                                                                        repo name                                                                                                                                            status
!xcp-ng-base                                                                                                                   XCP-ng Base Repository                                                                                                                               2,161
!xcp-ng-linstor                                                                                                                XCP-ng LINSTOR Repository                                                                                                                              142
!xcp-ng-updates                                                                                                                XCP-ng Updates Repository                                                                                                                            1,408
!zabbix/x86_64                                                                                                                 Zabbix Official Repository - x86_64                                                                                                                     79
!zabbix-non-supported/x86_64                                                                                                   Zabbix Official Repository non-supported - x86_64                                                                                                        6
repolist: 3,796
          J 1 Reply Last reply Reply Quote 0
          • V
            vaewyn
            last edited by

            Are there any rough estimates for timeline on paid support being available? Looking at ditching vmware and my company requires professional support availability. Virtualization I see the availability but I need storage as well that is at least mostly in parity with the vsan I have. Thanks to you all! Love these projects!

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

              We are working at full speed to get it available ASAP. There's still some bugs to fix and LINBIT is working on it.

              1 Reply Last reply Reply Quote 1
              • V
                vaewyn
                last edited by

                With the integration you are doing is there provision to designate racks/sites/datacenters/etc so at some level replications can be kept off hosts in the same physical risk space(s)?

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

                  XOSTOR works at the pool level. You can have all your hosts in the pool, or only some of them participating to the HCI (eg 4 hosts with disks used for HCI and others just consuming it). Obviously, it means some hosts without the disks will have to read and write "remotely" on the hosts with the disks. But it might be perfectly acceptable 🙂

                  V 1 Reply Last reply Reply Quote 0
                  • V
                    vaewyn @olivierlambert
                    last edited by

                    @olivierlambert I've understood that part... what I am wondering is if I have 3 hosts in one data center and 3 hosts in another, and I have asked for redundancy of 3 copies, is there a way to ensure all three copies are never in the same data center all at the same time.

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

                      So I imagine a very low latency between the 2 DCs? One pool with 6 hosts total and 3 per DC right?

                      For now, there's no placement preference, we need to discuss with LINBIT about topology.

                      And if the 2x DCs are far each other, I would advice to get 2x pools and use 2x XOSTOR total

                      V B 2 Replies Last reply Reply Quote 0
                      • V
                        vaewyn @olivierlambert
                        last edited by

                        @olivierlambert Correct... these DCs are across a campus on private fiber so single digit milliseconds worst case. We've historically had vmware keep 3 data copies and make sure at least one is in a separate DC... that way, when a DC is lost, the HA VMs can restart on the remaining host pool successfully because they have their storage available still.

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

                          So you can create a pool across the 2x DCs no problem. We'll take a deeper look on telling where to replicate to avoid having everything on the same place.

                          1 Reply Last reply Reply Quote 0
                          • B
                            BHellman 3rd party vendor @olivierlambert
                            last edited by

                            @olivierlambert said in XOSTOR hyperconvergence preview:

                            So I imagine a very low latency between the 2 DCs? One pool with 6 hosts total and 3 per DC right?

                            For now, there's no placement preference, we need to discuss with LINBIT about topology.

                            And if the 2x DCs are far each other, I would advice to get 2x pools and use 2x XOSTOR total

                            This can be done using placement policies as outlined in the LINSTOR users guide. It will probably require a bit of extra work on XO to use those properties

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

                              Technically, you could use manual CLI call to do it until we expose it in XO 🙂

                              1 Reply Last reply Reply Quote 2
                              • V
                                vaewyn
                                last edited by

                                For those that might run across my questions here... there is a nice blog post at Linbit on how to span availability zones correctly to keep your data redundancy up:
                                https://linbit.com/blog/multi-az-replication-using-automatic-placement-rules-in-linstor/

                                So CLI is doable 🙂 GUI would be nice in the future 😁

                                1 Reply Last reply Reply Quote 0
                                • J
                                  Jonathon @Jonathon
                                  last edited by

                                  @Jonathon said in XOSTOR hyperconvergence preview:

                                  @stormi said in XOSTOR hyperconvergence preview:

                                  yum repolist

                                  lol glad I checked then

                                  # yum repolist
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-linstor: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
repo id                                                                                                                        repo name                                                                                                                                            status
!xcp-ng-base                                                                                                                   XCP-ng Base Repository                                                                                                                               2,161
!xcp-ng-linstor                                                                                                                XCP-ng LINSTOR Repository                                                                                                                              142
!xcp-ng-updates                                                                                                                XCP-ng Updates Repository                                                                                                                            1,408
!zabbix/x86_64                                                                                                                 Zabbix Official Repository - x86_64                                                                                                                     79
!zabbix-non-supported/x86_64                                                                                                   Zabbix Official Repository non-supported - x86_64                                                                                                        6
repolist: 3,796

                                  I was wondering if anyone had any insight into this? Unable to upgrade xen hosts.

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

                                    @Jonathon I see no issue in this output, except that you enabled zabbix mirrors which might or might not play a role in your update issue.

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

                                      @stormi If you open a support tunnel and give me the ID in a private chat, I'll have a quick look.

                                      J 1 Reply Last reply Reply Quote 0
                                      • J
                                        Jonathon @stormi
                                        last edited by

                                        @stormi Message sent, thanks!

                                        No change if excluding zabbix

                                        [13:20 ovbh-pprod-xen10 ~]# yum update --disablerepo=zabbix*
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-linstor: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
Resolving Dependencies
--> Running transaction check
---> Package blktap.x86_64 0:3.37.4-1.0.1.0.linstor.1.xcpng8.2 will be updated
---> Package blktap.x86_64 0:3.37.4-2.1.xcpng8.2 will be an update
---> Package device-mapper-multipath.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated
---> Package device-mapper-multipath.x86_64 0:0.4.9-136.xcpng8.2 will be an update
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-136.xcpng8.2 will be an update
---> Package e2fsprogs.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package e2fsprogs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
--> Processing Dependency: libfuse.so.2(FUSE_2.5)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
--> Processing Dependency: libfuse.so.2(FUSE_2.6)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
--> Processing Dependency: libfuse.so.2(FUSE_2.8)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
--> Processing Dependency: libfuse.so.2()(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
---> Package e2fsprogs-libs.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package e2fsprogs-libs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
---> Package forkexecd.x86_64 0:1.18.1-1.1.xcpng8.2 will be updated
---> Package forkexecd.x86_64 0:1.18.3-3.1.xcpng8.2 will be an update
---> Package gpumon.x86_64 0:0.18.0-4.2.xcpng8.2 will be updated
---> Package gpumon.x86_64 0:0.18.0-11.2.xcpng8.2 will be an update
---> Package grub.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated
---> Package grub.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update
---> Package grub-efi.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated
---> Package grub-efi.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update
---> Package grub-tools.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated
---> Package grub-tools.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update
---> Package guest-templates-json.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package guest-templates-json-data-linux.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json-data-linux.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package guest-templates-json-data-other.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json-data-other.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package guest-templates-json-data-windows.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json-data-windows.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package http-nbd-transfer.x86_64 0:1.2.0-1.xcpng8.2 will be updated
---> Package http-nbd-transfer.x86_64 0:1.3.0-1.xcpng8.2 will be an update
---> Package irqbalance.x86_64 3:1.0.7-11.xcpng8.2 will be updated
---> Package irqbalance.x86_64 3:1.0.7-16.xcpng8.2 will be an update
---> Package kernel.x86_64 0:4.19.19-7.0.15.1.xcpng8.2 will be updated
---> Package kernel.x86_64 0:4.19.19-7.0.23.1.xcpng8.2 will be an update
---> Package kpartx.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated
---> Package kpartx.x86_64 0:0.4.9-136.xcpng8.2 will be an update
---> Package libcom_err.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package libcom_err.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
---> Package libss.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package libss.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
---> Package linux-firmware.noarch 0:20190314-5.1.xcpng8.2 will be updated
---> Package linux-firmware.noarch 0:20190314-10.2.xcpng8.2 will be an update
---> Package lldpad.x86_64 0:1.0.1-3.git036e314.xcpng8.2 will be updated
---> Package lldpad.x86_64 0:1.0.1-10.xcpng8.2 will be an update
---> Package message-switch.x86_64 0:1.23.2-3.2.xcpng8.2 will be updated
---> Package message-switch.x86_64 0:1.23.2-10.1.xcpng8.2 will be an update
---> Package microcode_ctl.x86_64 2:2.1-26.xs23.1.xcpng8.2 will be updated
---> Package microcode_ctl.x86_64 2:2.1-26.xs26.2.xcpng8.2 will be an update
---> Package nbd.x86_64 0:3.14-2.el7 will be updated
---> Package nbd.x86_64 0:3.24-1.xcpng8.2 will be an update
---> Package qemu.x86_64 2:4.2.1-4.6.2.1.xcpng8.2 will be updated
---> Package qemu.x86_64 2:4.2.1-4.6.3.1.xcpng8.2 will be an update
---> Package rrd2csv.x86_64 0:1.2.5-7.1.xcpng8.2 will be updated
---> Package rrd2csv.x86_64 0:1.2.6-8.1.xcpng8.2 will be an update
---> Package rrdd-plugins.x86_64 0:1.10.8-5.1.xcpng8.2 will be updated
---> Package rrdd-plugins.x86_64 0:1.10.9-5.1.xcpng8.2 will be an update
---> Package sm.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated
---> Package sm.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update
---> Package sm-cli.x86_64 0:0.23.0-7.xcpng8.2 will be updated
---> Package sm-cli.x86_64 0:0.23.0-54.1.xcpng8.2 will be an update
---> Package sm-rawhba.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated
---> Package sm-rawhba.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update
---> Package squeezed.x86_64 0:0.27.0-5.xcpng8.2 will be updated
---> Package squeezed.x86_64 0:0.27.0-11.1.xcpng8.2 will be an update
---> Package tzdata.noarch 0:2022a-1.el7 will be updated
---> Package tzdata.noarch 0:2023c-1.el7 will be an update
---> Package tzdata-java.noarch 0:2022a-1.el7 will be updated
---> Package tzdata-java.noarch 0:2023c-1.el7 will be an update
---> Package varstored-guard.x86_64 0:0.6.2-1.xcpng8.2 will be updated
---> Package varstored-guard.x86_64 0:0.6.2-8.xcpng8.2 will be an update
---> Package vendor-drivers.x86_64 0:1.0.2-1.3.xcpng8.2 will be updated
---> Package vendor-drivers.x86_64 0:1.0.2-1.6.xcpng8.2 will be an update
--> Processing Dependency: mpi3mr-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64
--> Processing Dependency: r8125-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64
--> Processing Dependency: igc-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64
---> Package vhd-tool.x86_64 0:0.43.0-4.1.xcpng8.2 will be updated
---> Package vhd-tool.x86_64 0:0.43.0-11.1.xcpng8.2 will be an update
---> Package wsproxy.x86_64 0:1.12.0-5.xcpng8.2 will be updated
---> Package wsproxy.x86_64 0:1.12.0-12.xcpng8.2 will be an update
---> Package xapi-core.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated
---> Package xapi-core.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update
---> Package xapi-nbd.x86_64 0:1.11.0-3.2.xcpng8.2 will be updated
---> Package xapi-nbd.x86_64 0:1.11.0-10.1.xcpng8.2 will be an update
---> Package xapi-storage.x86_64 0:11.19.0_sxm2-3.xcpng8.2 will be updated
---> Package xapi-storage.x86_64 0:11.19.0_sxm2-10.xcpng8.2 will be an update
---> Package xapi-storage-script.x86_64 0:0.34.1-2.1.xcpng8.2 will be updated
---> Package xapi-storage-script.x86_64 0:0.34.1-9.1.xcpng8.2 will be an update
---> Package xapi-tests.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated
---> Package xapi-tests.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update
---> Package xapi-xe.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated
---> Package xapi-xe.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update
---> Package xcp-networkd.x86_64 0:0.56.2-1.xcpng8.2 will be updated
---> Package xcp-networkd.x86_64 0:0.56.2-8.xcpng8.2 will be an update
---> Package xcp-ng-linstor.noarch 0:1.0-1.xcpng8.2 will be updated
---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update
--> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch
---> Package xcp-ng-release.x86_64 0:8.2.1-6 will be updated
---> Package xcp-ng-release.x86_64 0:8.2.1-10 will be an update
---> Package xcp-ng-release-config.x86_64 0:8.2.1-6 will be updated
---> Package xcp-ng-release-config.x86_64 0:8.2.1-10 will be an update
---> Package xcp-ng-release-linstor.noarch 0:1.2-1.xcpng8.2 will be updated
---> Package xcp-ng-release-linstor.noarch 0:1.3-1.xcpng8.2 will be an update
---> Package xcp-ng-release-presets.x86_64 0:8.2.1-6 will be updated
---> Package xcp-ng-release-presets.x86_64 0:8.2.1-10 will be an update
---> Package xcp-ng-xapi-plugins.noarch 0:1.7.2-1.0.0.linstor.1.xcpng8.2 will be updated
---> Package xcp-ng-xapi-plugins.noarch 0:1.8.0-1.xcpng8.2 will be an update
---> Package xcp-rrdd.x86_64 0:1.33.0-6.1.xcpng8.2 will be updated
---> Package xcp-rrdd.x86_64 0:1.33.2-7.1.xcpng8.2 will be an update
---> Package xen-dom0-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-dom0-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-dom0-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-dom0-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-hypervisor.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-hypervisor.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xenopsd.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated
---> Package xenopsd.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update
---> Package xenopsd-cli.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated
---> Package xenopsd-cli.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update
---> Package xenopsd-xc.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated
---> Package xenopsd-xc.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update
---> Package xs-openssl-libs.x86_64 1:1.1.1k-6.1.xcpng8.2 will be updated
---> Package xs-openssl-libs.x86_64 1:1.1.1k-9.1.xcpng8.2 will be an update
--> Running transaction check
---> Package fuse-libs.x86_64 0:2.9.2-10.xcpng8.2 will be installed
---> Package igc-module.x86_64 0:5.10.200-1.xcpng8.2 will be installed
---> Package mpi3mr-module.x86_64 0:8.6.1.0.0-1.xcpng8.2 will be installed
---> Package r8125-module.x86_64 0:9.012.03-1.xcpng8.2 will be installed
---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update
--> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch
--> Finished Dependency Resolution
Error: Package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch (xcp-ng-updates)
           Requires: sm-linstor
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
                                        stormiS 1 Reply Last reply Reply Quote 0
                                        • stormiS
                                          stormi Vates 🪐 XCP-ng Team @Jonathon
                                          last edited by

                                          @Jonathon Ok, here's the solution, and the explanation:

                                          First, just update xcp-ng-release-linstor. This will update the repository file for linstor-related RPMs to make it point to a newer repository, located at a different place.

                                          Then updating the rest of the system will become possible again.

                                          J 2 Replies Last reply Reply Quote 0
                                          • J
                                            Jonathon @stormi
                                            last edited by

                                            @stormi

                                            Unfortunately does not look like that works. Unless I am doing something wrong.

                                            [12:26 ovbh-pprod-xen10 ~]# yum update xcp-ng-release-linstor
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-linstor: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
Resolving Dependencies
--> Running transaction check
---> Package xcp-ng-release-linstor.noarch 0:1.2-1.xcpng8.2 will be updated
---> Package xcp-ng-release-linstor.noarch 0:1.3-1.xcpng8.2 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

==========================================================================================================================================================================================================================================================================================
 Package                                                                     Arch                                                        Version                                                                Repository                                                           Size
==========================================================================================================================================================================================================================================================================================
Updating:
 xcp-ng-release-linstor                                                      noarch                                                      1.3-1.xcpng8.2                                                         xcp-ng-updates                                                      4.0 k

Transaction Summary
==========================================================================================================================================================================================================================================================================================
Upgrade  1 Package

Total download size: 4.0 k
Is this ok [y/d/N]: y
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
xcp-ng-release-linstor-1.3-1.xcpng8.2.noarch.rpm                                                                                                                                                                                                                   | 4.0 kB  00:00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : xcp-ng-release-linstor-1.3-1.xcpng8.2.noarch                                                                                                                                                                                                                           1/2 
  Cleanup    : xcp-ng-release-linstor-1.2-1.xcpng8.2.noarch                                                                                                                                                                                                                           2/2 
  Verifying  : xcp-ng-release-linstor-1.3-1.xcpng8.2.noarch                                                                                                                                                                                                                           1/2 
  Verifying  : xcp-ng-release-linstor-1.2-1.xcpng8.2.noarch                                                                                                                                                                                                                           2/2 

Updated:
  xcp-ng-release-linstor.noarch 0:1.3-1.xcpng8.2                                                                                                                                                                                                                                          

Complete!
[12:26 ovbh-pprod-xen10 ~]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
Resolving Dependencies
--> Running transaction check
---> Package blktap.x86_64 0:3.37.4-1.0.1.0.linstor.1.xcpng8.2 will be updated
---> Package blktap.x86_64 0:3.37.4-2.1.xcpng8.2 will be an update
---> Package device-mapper-multipath.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated
---> Package device-mapper-multipath.x86_64 0:0.4.9-136.xcpng8.2 will be an update
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-136.xcpng8.2 will be an update
---> Package e2fsprogs.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package e2fsprogs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
--> Processing Dependency: libfuse.so.2(FUSE_2.5)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
--> Processing Dependency: libfuse.so.2(FUSE_2.6)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
--> Processing Dependency: libfuse.so.2(FUSE_2.8)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
--> Processing Dependency: libfuse.so.2()(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64
---> Package e2fsprogs-libs.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package e2fsprogs-libs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
---> Package forkexecd.x86_64 0:1.18.1-1.1.xcpng8.2 will be updated
---> Package forkexecd.x86_64 0:1.18.3-3.1.xcpng8.2 will be an update
---> Package gpumon.x86_64 0:0.18.0-4.2.xcpng8.2 will be updated
---> Package gpumon.x86_64 0:0.18.0-11.2.xcpng8.2 will be an update
---> Package grub.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated
---> Package grub.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update
---> Package grub-efi.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated
---> Package grub-efi.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update
---> Package grub-tools.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated
---> Package grub-tools.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update
---> Package guest-templates-json.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package guest-templates-json-data-linux.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json-data-linux.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package guest-templates-json-data-other.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json-data-other.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package guest-templates-json-data-windows.noarch 0:1.9.6-1.2.xcpng8.2 will be updated
---> Package guest-templates-json-data-windows.noarch 0:1.10.6-1.1.xcpng8.2 will be an update
---> Package http-nbd-transfer.x86_64 0:1.2.0-1.xcpng8.2 will be updated
---> Package http-nbd-transfer.x86_64 0:1.3.0-1.xcpng8.2 will be an update
---> Package irqbalance.x86_64 3:1.0.7-11.xcpng8.2 will be updated
---> Package irqbalance.x86_64 3:1.0.7-16.xcpng8.2 will be an update
---> Package kernel.x86_64 0:4.19.19-7.0.15.1.xcpng8.2 will be updated
---> Package kernel.x86_64 0:4.19.19-7.0.23.1.xcpng8.2 will be an update
---> Package kpartx.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated
---> Package kpartx.x86_64 0:0.4.9-136.xcpng8.2 will be an update
---> Package libcom_err.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package libcom_err.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
---> Package libss.x86_64 0:1.42.9-12.el7_5 will be updated
---> Package libss.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update
---> Package linux-firmware.noarch 0:20190314-5.1.xcpng8.2 will be updated
---> Package linux-firmware.noarch 0:20190314-10.2.xcpng8.2 will be an update
---> Package lldpad.x86_64 0:1.0.1-3.git036e314.xcpng8.2 will be updated
---> Package lldpad.x86_64 0:1.0.1-10.xcpng8.2 will be an update
---> Package message-switch.x86_64 0:1.23.2-3.2.xcpng8.2 will be updated
---> Package message-switch.x86_64 0:1.23.2-10.1.xcpng8.2 will be an update
---> Package microcode_ctl.x86_64 2:2.1-26.xs23.1.xcpng8.2 will be updated
---> Package microcode_ctl.x86_64 2:2.1-26.xs26.2.xcpng8.2 will be an update
---> Package nbd.x86_64 0:3.14-2.el7 will be updated
---> Package nbd.x86_64 0:3.24-1.xcpng8.2 will be an update
---> Package qemu.x86_64 2:4.2.1-4.6.2.1.xcpng8.2 will be updated
---> Package qemu.x86_64 2:4.2.1-4.6.3.1.xcpng8.2 will be an update
---> Package rrd2csv.x86_64 0:1.2.5-7.1.xcpng8.2 will be updated
---> Package rrd2csv.x86_64 0:1.2.6-8.1.xcpng8.2 will be an update
---> Package rrdd-plugins.x86_64 0:1.10.8-5.1.xcpng8.2 will be updated
---> Package rrdd-plugins.x86_64 0:1.10.9-5.1.xcpng8.2 will be an update
---> Package sm.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated
---> Package sm.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update
---> Package sm-cli.x86_64 0:0.23.0-7.xcpng8.2 will be updated
---> Package sm-cli.x86_64 0:0.23.0-54.1.xcpng8.2 will be an update
---> Package sm-rawhba.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated
---> Package sm-rawhba.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update
---> Package squeezed.x86_64 0:0.27.0-5.xcpng8.2 will be updated
---> Package squeezed.x86_64 0:0.27.0-11.1.xcpng8.2 will be an update
---> Package tzdata.noarch 0:2022a-1.el7 will be updated
---> Package tzdata.noarch 0:2023c-1.el7 will be an update
---> Package tzdata-java.noarch 0:2022a-1.el7 will be updated
---> Package tzdata-java.noarch 0:2023c-1.el7 will be an update
---> Package varstored-guard.x86_64 0:0.6.2-1.xcpng8.2 will be updated
---> Package varstored-guard.x86_64 0:0.6.2-8.xcpng8.2 will be an update
---> Package vendor-drivers.x86_64 0:1.0.2-1.3.xcpng8.2 will be updated
---> Package vendor-drivers.x86_64 0:1.0.2-1.6.xcpng8.2 will be an update
--> Processing Dependency: mpi3mr-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64
--> Processing Dependency: r8125-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64
--> Processing Dependency: igc-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64
---> Package vhd-tool.x86_64 0:0.43.0-4.1.xcpng8.2 will be updated
---> Package vhd-tool.x86_64 0:0.43.0-11.1.xcpng8.2 will be an update
---> Package wsproxy.x86_64 0:1.12.0-5.xcpng8.2 will be updated
---> Package wsproxy.x86_64 0:1.12.0-12.xcpng8.2 will be an update
---> Package xapi-core.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated
---> Package xapi-core.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update
---> Package xapi-nbd.x86_64 0:1.11.0-3.2.xcpng8.2 will be updated
---> Package xapi-nbd.x86_64 0:1.11.0-10.1.xcpng8.2 will be an update
---> Package xapi-storage.x86_64 0:11.19.0_sxm2-3.xcpng8.2 will be updated
---> Package xapi-storage.x86_64 0:11.19.0_sxm2-10.xcpng8.2 will be an update
---> Package xapi-storage-script.x86_64 0:0.34.1-2.1.xcpng8.2 will be updated
---> Package xapi-storage-script.x86_64 0:0.34.1-9.1.xcpng8.2 will be an update
---> Package xapi-tests.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated
---> Package xapi-tests.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update
---> Package xapi-xe.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated
---> Package xapi-xe.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update
---> Package xcp-networkd.x86_64 0:0.56.2-1.xcpng8.2 will be updated
---> Package xcp-networkd.x86_64 0:0.56.2-8.xcpng8.2 will be an update
---> Package xcp-ng-linstor.noarch 0:1.0-1.xcpng8.2 will be updated
---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update
--> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch
---> Package xcp-ng-release.x86_64 0:8.2.1-6 will be updated
---> Package xcp-ng-release.x86_64 0:8.2.1-10 will be an update
---> Package xcp-ng-release-config.x86_64 0:8.2.1-6 will be updated
---> Package xcp-ng-release-config.x86_64 0:8.2.1-10 will be an update
---> Package xcp-ng-release-presets.x86_64 0:8.2.1-6 will be updated
---> Package xcp-ng-release-presets.x86_64 0:8.2.1-10 will be an update
---> Package xcp-ng-xapi-plugins.noarch 0:1.7.2-1.0.0.linstor.1.xcpng8.2 will be updated
---> Package xcp-ng-xapi-plugins.noarch 0:1.8.0-1.xcpng8.2 will be an update
---> Package xcp-rrdd.x86_64 0:1.33.0-6.1.xcpng8.2 will be updated
---> Package xcp-rrdd.x86_64 0:1.33.2-7.1.xcpng8.2 will be an update
---> Package xen-dom0-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-dom0-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-dom0-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-dom0-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-hypervisor.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-hypervisor.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xen-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated
---> Package xen-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update
---> Package xenopsd.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated
---> Package xenopsd.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update
---> Package xenopsd-cli.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated
---> Package xenopsd-cli.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update
---> Package xenopsd-xc.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated
---> Package xenopsd-xc.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update
---> Package xs-openssl-libs.x86_64 1:1.1.1k-6.1.xcpng8.2 will be updated
---> Package xs-openssl-libs.x86_64 1:1.1.1k-9.1.xcpng8.2 will be an update
---> Package zabbix-agent.x86_64 0:7.0.0-alpha3.release1.el7 will be updated
---> Package zabbix-agent.x86_64 0:7.0.0-beta1.release1.el7 will be an update
--> Running transaction check
---> Package fuse-libs.x86_64 0:2.9.2-10.xcpng8.2 will be installed
---> Package igc-module.x86_64 0:5.10.200-1.xcpng8.2 will be installed
---> Package mpi3mr-module.x86_64 0:8.6.1.0.0-1.xcpng8.2 will be installed
---> Package r8125-module.x86_64 0:9.012.03-1.xcpng8.2 will be installed
---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update
--> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch
--> Finished Dependency Resolution
Error: Package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch (xcp-ng-updates)
           Requires: sm-linstor
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post