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

    XCP-ng 8.2 updates announcements and testing

    Scheduled Pinned Locked Moved News
    703 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.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team
      last edited by

      Were you using sudo on the host before?

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

        @stormi No just default install

        1 Reply Last reply Reply Quote 0
        • stormiS Offline
          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?

          brezlordB 1 Reply Last reply Reply Quote 0
          • brezlordB Offline
            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
            • brezlordB Offline
              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
              • stormiS Offline
                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.

                brezlordB 1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  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
                  • brezlordB Offline
                    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
                    • olivierlambertO Offline
                      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).

                      brezlordB 1 Reply Last reply Reply Quote 0
                      • brezlordB Offline
                        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
                        • stormiS Offline
                          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.

                          brezlordB 1 Reply Last reply Reply Quote 0
                          • brezlordB Offline
                            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
                            • stormiS Offline
                              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
                              • brezlordB Offline
                                brezlord
                                last edited by

                                @stormi you can download the logs here.

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

                                  I see this in daemon.log, a message from systemd attempting to shut the system down:

                                  Feb  1 22:11:35 xcp-ng-01 systemd[1]: Unmounted /run/sr-mount/5f5a9343-b95a-9bfa-bd3a-bc30d7368058.
                                  Feb  1 22:11:35 xcp-ng-01 systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
                                  Feb  1 22:11:35 xcp-ng-01 systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
                                  Feb  1 22:11:35 xcp-ng-01 systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
                                  Feb  1 22:11:35 xcp-ng-01 systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
                                  Feb  1 22:11:35 xcp-ng-01 systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
                                  

                                  There definitely was a network mountpoint (a NFS SR) which was not connected anymore. This explains the long reboot time.

                                  Going up the logs, I see this:

                                  Feb  1 22:01:43 xcp-ng-01 systemd[1]: xenopsd-xc.service: main process exited, code=exited, status=2/INVALIDARGUMENT
                                  Feb  1 22:01:43 xcp-ng-01 systemd[1]: Unit xenopsd-xc.service entered failed state.
                                  Feb  1 22:01:43 xcp-ng-01 systemd[1]: xenopsd-xc.service failed.
                                  

                                  This explains the failed XAPI restart and is likely the known issue with xenopsd I mentioned above.

                                  So, if I'm not wrong, it's good news:

                                  • The xenospd issue is known and a fix is on its way and usually disappears after a reboot.
                                  • The update itself probably didn't cause your issues.
                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambertO Offline
                                    olivierlambert Vates 🪐 Co-Founder CEO
                                    last edited by

                                    haha my "gut feeling" © approved 😄

                                    1 Reply Last reply Reply Quote 0
                                    • N Offline
                                      NielsH @gduperrey
                                      last edited by

                                      @gduperrey said in Updates announcements and testing:

                                      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.

                                      Hello,

                                      Is there any update on the ETA for this? Since it has been almost a month. We'll do the xcp-ng updates again soon and if these patches are close to release we will wait for them to prevent double work.

                                      Cheers,
                                      Niels

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

                                        @NielsH We'll wait for the next security update, to ship them together. When exactly security updates are released can't always be predicted or disclosed.

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

                                          New Security Update Candidates (Xen, microcode, ...)

                                          Components are updated to fix vulnerabilities:

                                          • Xen is updated to fix XSA-426. It also includes the previous change which had not been released yet: Enable AVX-512 by default for EPYC Zen4 (Genoa)
                                          • Intel and AMD microcode is updated for various devices:
                                            • Intel update (which in turn links to the advisories)
                                            • AMD advisory

                                          We will also release at the same time:

                                          • xcp-ng-release-*: fixes benign but annoying fcoe-related error messages at boot

                                          And an update candidate which has been tested previously:

                                          • Guest templates: added 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:

                                          yum clean metadata --enablerepo=xcp-ng-testing
                                          yum update "guest-templates-*" "xen-*" microcode_ctl linux-firmware "xcp-ng-release-*" --enablerepo=xcp-ng-testing
                                          reboot
                                          

                                          Versions:

                                          • xen-*: 4.13.4-9.29.2.xcpng8.2
                                          • microcode_ctl: 2.1-26.xs23.1.xcpng8.2
                                          • linux-firmware: 20190314-5.1.xcpng8.2
                                          • guest-templates-json-*: 1.9.6-1.2.xcpng8.2
                                          • xcp-ng-release-*: 8.2.1-6

                                          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

                                          48h

                                          A M 2 Replies Last reply Reply Quote 1
                                          • A Offline
                                            Andrew Top contributor @stormi
                                            last edited by

                                            @stormi I'm running the update on all 8.2.1 hosts. No problems so far.

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