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

    XCP-ng 8.2 updates announcements and testing

    Scheduled Pinned Locked Moved News
    708 Posts 67 Posters 1.1m Views 86 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.
    • gskgerG Offline
      gskger Top contributor @stormi
      last edited by

      @stormi All good with updating my playlab.

      1 Reply Last reply Reply Quote 2
      • J Offline
        JeffBerntsen Top contributor @stormi
        last edited by

        Seems to be working fine for me as well.

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

          We found and fixed a regression in the update candidate for sm regarding shared thick-provisioned drivers based on LVM (lvmoiscsi and others).

          Please update again (mirrors will receive the within 15 minutes) using the command given above. This will give you sm and sm-rawhba in version-release 2.30.7-1.3.xcpng8.2.

          gskgerG A 2 Replies Last reply Reply Quote 0
          • gskgerG Offline
            gskger Top contributor @stormi
            last edited by

            @stormi Can not help with the sm and sm-rawhba regression, but did the update anyway. Worked well and kicking some VMs around works as expected. Let's see how my playlab does during the weekend.

            1 Reply Last reply Reply Quote 1
            • A Offline
              AlexD2006 @stormi
              last edited by

              @stormi
              is there some information about that regression?
              maybe i can help to test.
              have a lab pool here with 3 hosts on a iscsi SR.

              stormiS 1 Reply Last reply Reply Quote 0
              • B Offline
                busthead
                last edited by

                Hello,

                This thread appears to be for testing update candidate releases. Where can I find the release notes for production ready updates?

                Thx

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

                  Any functional change will be explained in our blog. Other updates are mostly security (see the security tag on the blog: https://xcp-ng.org/blog/tag/security)

                  Also https://xcp-ng.org/blog/tag/update

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

                    New security update (xen, Intel and AMD CPUs)

                    Xen is being updated to mitigate hardware vulnerabilities in Intel and AMD CPUs.

                    • Upstream (Xen project) advisory: XSA-407
                    • Citrix Hypervisor Security Bulletin: https://support.citrix.com/article/CTX461397/citrix-hypervisor-security-bulletin-for-cve202223816-and-cve202223825

                    Impact of the vulnerabilities - RETbleed is a speculative execution attack on x86-64 processors, including some recent Intel and AMD chips. You can read the original paper from Computer Security Group at this address: https://comsec.ethz.ch/research/microarch/retbleed/

                    Test on XCP-ng 8.2

                    From an up to date host:

                    yum clean metadata --enablerepo=xcp-ng-testing
                    yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools --enablerepo=xcp-ng-testing
                    reboot
                    

                    Versions:

                    • xen-*: 4.13.4-9.24.1.xcpng8.2

                    What to test

                    Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better.

                    Test window before official release of the updates

                    ~2 days.

                    J gskgerG 2 Replies Last reply Reply Quote 2
                    • olivierlambertO Offline
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      Tested in my lab, so far so good.

                      More testers means faster release 🙂

                      1 Reply Last reply Reply Quote 1
                      • J Offline
                        JeffBerntsen Top contributor @gduperrey
                        last edited by

                        @gduperrey This update breaks the XOSTOR setup in my test lab. Would you like any information from me for troubleshooting? If not, what's the easiest way to revert the test updates?

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

                          Hmm no reason for that, did you have other updates coming with it? (ie replacing some other unrelated packages).

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

                            Adding @ronan-a in the loop.

                            When you said "break", can you be more specific @JeffBerntsen ?

                            J 1 Reply Last reply Reply Quote 0
                            • J Offline
                              JeffBerntsen Top contributor @olivierlambert
                              last edited by

                              @olivierlambert said in Updates announcements and testing:

                              Adding @ronan-a in the loop.

                              When you said "break", can you be more specific @JeffBerntsen ?

                              @olivierlambert said in Updates announcements and testing:

                              Hmm no reason for that, did you have other updates coming with it? (ie replacing some other unrelated packages).

                              I have 3 servers in my lab's test pool, vh97, vh98, and vh99. Server vh97 was the pool master. I placed it into maintenance mode and shifted the pool master to vh98 in the process, installed the updates, and rebooted.

                              When vh97 came back up, it could no longer attach to the XOSTOR SR. Attempting to replug the PBD gives me errors indicating that vh97 can no longer see the SR. It appears that there are some related errors in the SMlog file (I've captured a copy for future examination).

                              The updates installed were only the ones from this most recent set. All of the other test updates from this thread from the last two weeks were already installed and running without problems on all 3 servers in the pool.

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

                                If you test XOSTOR, don't test other updates, because this might break the rest.

                                Also, never switch the master after updates, the master HAS to reboot first, whatever happens.

                                J 1 Reply Last reply Reply Quote 0
                                • J Offline
                                  JeffBerntsen Top contributor @olivierlambert
                                  last edited by

                                  @olivierlambert said in Updates announcements and testing:

                                  If you test XOSTOR, don't test other updates, because this might break the rest.

                                  Also, never switch the master after updates, the master HAS to reboot first, whatever happens.

                                  I know that XOSTOR might break during an update test. I thought whether it did or didn't might be something you would be interested in as part of testing and that's part of why I test with it in place and running.

                                  1 Reply Last reply Reply Quote 1
                                  • ronan-aR Offline
                                    ronan-a Vates 🪐 XCP-ng Team @JeffBerntsen
                                    last edited by

                                    @JeffBerntsen What's your sm version? I suppose, you updated your hosts and you don't have the right one.

                                    Please send me the output of: rpm -qa | grep sm-. 🙂

                                    J 1 Reply Last reply Reply Quote 0
                                    • J Offline
                                      JeffBerntsen Top contributor @ronan-a
                                      last edited by

                                      @ronan-a said in Updates announcements and testing:

                                      @JeffBerntsen What's your sm version? I suppose, you updated your hosts and you don't have the right one.

                                      Please send me the output of: rpm -qa | grep sm-. 🙂

                                      Definitely possible although it appears they were updated as part of installing the previous updates in this thread from the past couple of weeks.

                                      What I have is:

                                      sm-cli-0.23.0-6.xcpng8.2.x86_64
                                      sm-rawhba-2.30.7-1.3.xcpng8.2.x86_64
                                      sm-2.30.7-1.3.xcpng8.2.x86_64
                                      
                                      ronan-aR 1 Reply Last reply Reply Quote 0
                                      • ronan-aR Offline
                                        ronan-a Vates 🪐 XCP-ng Team @JeffBerntsen
                                        last edited by

                                        @JeffBerntsen I think I will release a new linstor RPM to override the sm testing package. The current is: sm-2.30.7-1.2.0.linstor.1.xcpng8.2.x86_64.rpm. For the moment, you can downgrade if you want. 🙂

                                        J 1 Reply Last reply Reply Quote 0
                                        • J Offline
                                          JeffBerntsen Top contributor @ronan-a
                                          last edited by

                                          @ronan-a said in Updates announcements and testing:

                                          @JeffBerntsen I think I will release a new linstor RPM to override the sm testing package. The current is: sm-2.30.7-1.2.0.linstor.1.xcpng8.2.x86_64.rpm. For the moment, you can downgrade if you want. 🙂

                                          That seems to have taken care of it. Left all upgraded versions from this thread in place except for sm and sm-rawhba which have been downgraded to the linstor versions from the regular repo. All seems to be working well now.

                                          1 Reply Last reply Reply Quote 1
                                          • gskgerG Offline
                                            gskger Top contributor @gduperrey
                                            last edited by

                                            @gduperrey Updating my playlab and all is good with some easy VM operations and VM/storage migration test. Now let's see how the next few days of normal tasks turn out.

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