XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Updates announcements and testing

    News
    61
    545
    192674
    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.
    • gduperrey
      gduperrey Vates πŸͺ XCP-ng Team πŸš€ last edited by

      New Update Candidates (xen, xapi, templates)

      • Xen: Enable AVX-512 by default for EPYC Zen4 (Genoa)
      • Xapi: Redirect http requests on the host webpage to https by default.
      • Guest templates:
        • Add the following templates: RHEL 9, AlmaLinux 9, Rocky Linux 9, CentOS Stream 8 & 9, Oracle Linux 9

      Test on XCP-ng 8.2

      From an up to date host:

      For Xen, Xapi and Guest templates:

      yum clean metadata --enablerepo=xcp-ng-testing
      yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools xapi-core xapi-tests xapi-xe guest-templates-json guest-templates-json-data-linux guest-templates-json-data-other guest-templates-json-data-windows --enablerepo=xcp-ng-testing
      reboot
      

      Versions:

      • xen-*: 4.13.4-9.29.1.xcpng8.2
      • xapi-*: 1.249.26-2.2.xcpng8.2
      • guest-templates-json-*: 1.9.6-1.2.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

      No precise ETA, but the sooner the feedback the better.

      A N 3 Replies Last reply Reply Quote 0
      • A
        Andrew Top contributor πŸ’ͺ @gduperrey last edited by

        @gduperrey Mirror error

        failure: repodata/6b271e84b07dced2015bb0d835fb0ec1be1d308d92010993d44a1af0c130aa9f-primary.sqlite.bz2 from xcp-ng-testing: [Errno 256] No more mirrors to try.
        http://mirrors.xcp-ng.org/8/8.2/testing/x86_64/repodata/6b271e84b07dced2015bb0d835fb0ec1be1d308d92010993d44a1af0c130aa9f-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
        
        Name:   mirrors.xcp-ng.org
        Address: 37.26.189.194
        
        1 Reply Last reply Reply Quote 0
        • A
          Andrew Top contributor πŸ’ͺ @gduperrey last edited by

          @gduperrey The repository seems to work now....

          1 Reply Last reply Reply Quote 1
          • Referenced by  lightingman117 lightingman117 
          • stormi
            stormi Vates πŸͺ XCP-ng Team πŸš€ last edited by

            Unrelated to the above: a security update for sudo was published. I don't think it's very likely to be an actual threat in the context of your use of XCP-ng, but it might be in specific contexts.

            https://xcp-ng.org/blog/2023/01/31/january-2023-security-update/

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

              @stormi Applied the update through XO and now XO can not login to the host with the below error.

              connect ECONNREFUSED 192.168.40.201:443
              

              I rebooted the host and I can no longer login as root.

              ssh: connect to host 192.168.40.201 port 22: Connection refused
              

              Any ideas?

              1 Reply Last reply Reply Quote 0
              • stormi
                stormi Vates πŸͺ XCP-ng Team πŸš€ last edited by stormi

                Was it the only update applied? Is the stunnel service running?

                Oh, I also read that you can't connect as root.

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

                  @stormi Yes only update.

                  1 Reply Last reply Reply Quote 0
                  • stormi
                    stormi Vates πŸͺ XCP-ng Team πŸš€ last edited by

                    Were you using sudo on the host before?

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

                      @stormi No just default install

                      1 Reply Last reply Reply Quote 0
                      • stormi
                        stormi Vates πŸͺ XCP-ng Team πŸš€ last edited by

                        I hardly see a cause-effect link between the update and the issues (both SSH and XAPI not responding anymore?), but computers are full of surprises.

                        Did you change the firewall configuration? Could the IP address have changed or the same be attributed to another device?

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

                          @stormi Done nothing but apply the update through XO web console. I have yanked the plug and making sure it actually reboots.

                          1 Reply Last reply Reply Quote 0
                          • brezlord
                            brezlord last edited by

                            That fixed it I can login via ssh with root and XO sees the host.

                            1 Reply Last reply Reply Quote 0
                            • stormi
                              stormi Vates πŸͺ XCP-ng Team πŸš€ last edited by

                              Maybe it was still rebooting, stuck on the shutdown phase, waiting for some kind of I/O or something. This would explain why it didn't respond.

                              brezlord 1 Reply Last reply Reply Quote 0
                              • olivierlambert
                                olivierlambert Vates πŸͺ Co-Founder🦸 CEO πŸ§‘β€πŸ’Ό last edited by olivierlambert

                                I concur. If the shutdown process is stuck somewhere (eg an NFS share), you can't connect at all (connection refused in SSH, no XAPI connection) and it can stays like this for a while.

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

                                  @stormi It was not responding after the update from XO. I could long in via ssh and restarted the tool stack but this did not help XO still could not login. I issued a reboot command via ssh which dropped the ssh session and the host did not reboot most likely due to running VMs. I then yanked the power and the host rebooted and everything is working as it should. The update definitely caused the issue.

                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambert
                                    olivierlambert Vates πŸͺ Co-Founder🦸 CEO πŸ§‘β€πŸ’Ό last edited by

                                    I did update my home lab without any issue, before, during and after the update (I did test just after the update without any reboot).

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

                                      @olivierlambert This is my home lab as well running on a small form factor PC with an Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz

                                      1 Reply Last reply Reply Quote 0
                                      • stormi
                                        stormi Vates πŸͺ XCP-ng Team πŸš€ last edited by stormi

                                        XO restarts the toolstack after installing updates. So what first went wrong is this: it couldn't restart. You can't say for sure it's caused by the update, because there are many other reasons that can make this fail. The logs would tell. For example a known bug, being fixed, in xenospd-xc, which makes it unable to restart when something specific happened to VM metadata.

                                        So we'll keep an eye and ears open for any other occurrence of this issue in relation with the update, but I still think there's little chance an update of sudo would itself cause this.

                                        We'll do a few additional tests to see if we can reproduce.

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

                                          @stormi If you direct me to where the log you need are I can provide them.

                                          1 Reply Last reply Reply Quote 0
                                          • stormi
                                            stormi Vates πŸͺ XCP-ng Team πŸš€ last edited by

                                            /var/log/xensource.log and /var/log/daemon.log would be the first ones to check.

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