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

    XCP-ng 8.2.1 (maintenance update) - final testing sprint

    Scheduled Pinned Locked Moved News
    40 Posts 8 Posters 14.5k 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.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team
      last edited by

      The error message suggests an internal network error message. Does this host have custom iptables rules, or xapi.conf entries?

      apzA 1 Reply Last reply Reply Quote 0
      • apzA Offline
        apz @stormi
        last edited by

        @stormi I have not touched xapi.conf, iptables has one additional rule to default, which allows port 4949 in. It's copy-paste of other rules in /etc/sysconfig/iptables, save changed port.

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

          @apz Are there differences between the installed hosts that could be a lead? Could you compare the lists of installed RPMs between your hosts? (rpm -qa | sort). Is the network configuration different?

          Are there error logs in xensource.log, user.log, daemon.log when you run /usr/bin/create-guest-templates-wrapper?

          apzA 1 Reply Last reply Reply Quote 0
          • apzA Offline
            apz @stormi
            last edited by

            @stormi I diffed this host (originally installed as 8.2.0) and one I installed very recently (during 8.2.1 testing phase). Their differences are:

            137d136
            < igc-module-4.20.17-1.xcpng8.2.x86_64
            274a274
            > MegaCli-8.07.14-1.noarch
            394d393
            < r8125-module-9.003.05-1.xcpng8.2.x86_64
            

            The 8.2.1 installation appears to have network card modules in packages, the old installation has MegaCLI installed because of its RAID controller.

            xensource.log is attached, user.log didn't yield anything, neither did daemon.log

            As I was running this command again and again, it succeeded once. Out of curiosity, I tried running it again and again on my other hosts that had succeeded the last time. I could introduce a random failure on all of them, maybe 1 out of 20 or more rare.

            xensource.txt

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

              @apz It's not related to your issue, but you need to read https://xcp-ng.org/forum/post/47128

              apzA 1 Reply Last reply Reply Quote 0
              • apzA Offline
                apz @stormi
                last edited by

                @stormi The other (working) machine is indeed installed with test5.

                Should I care about the fact that the testing repo no longer exists, so the two first commands fail?

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

                  @apz If you removed the repo file for staging you can just remove the --enablerepo part.

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    mortenchristensn
                    last edited by

                    Tried to update my homelab from 8.2 to 8.2.1 with the iso on usb.

                    After having answered all questions, the installer stops with

                    Error occurred
                    An unrecoverable error has occurred. The error was:
                    Installer mode (UEFI) is mismatched with target boot
                    mode (legacy)
                    Reboot

                    Can I choose between legacy and uefi somewhere?
                    Do I have to change my bios-settings from legacy to uefi, and can it damage my working installation?

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

                      @mortenchristensn I see two mistakes here:

                      1. the process to update from 8.2 to 8.2.1 is not by using the ISO. Check the blog post.
                      2. when you want to upgrade a host using the ISO, you need to make sure you boot the ISO in the same mode as the installed system (BIOS vs UEFI).
                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        mortenchristensn @stormi
                        last edited by

                        @stormi said in XCP-ng 8.2.1 (maintenance update) - final testing sprint:

                        @mortenchristensn I see two mistakes here:

                        1. the process to update from 8.2 to 8.2.1 is not by using the ISO. Check the blog post.

                        Can it be rolled back to a working 8.2, if it is updated with "yum update" ?
                        I have a server with similar motherboard running 8.1. Is that recommended to upgrade with "yum update" too ?

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

                          @mortenchristensn said in XCP-ng 8.2.1 (maintenance update) - final testing sprint:

                          @stormi said in XCP-ng 8.2.1 (maintenance update) - final testing sprint:

                          @mortenchristensn I see two mistakes here:

                          1. the process to update from 8.2 to 8.2.1 is not by using the ISO. Check the blog post.

                          Can it be rolled back to a working 8.2, if it is updated with "yum update" ?

                          Not exactly, but you can downgrade RPMs individually if really needed.

                          I have a server with similar motherboard running 8.1. Is that recommended to upgrade with "yum update" too ?

                          In this situation it's your choice. If you want to have a backup you can rollback to, you should favour the ISO.

                          K 1 Reply Last reply Reply Quote 0
                          • K Offline
                            KPS Top contributor @stormi
                            last edited by

                            Hi!

                            I am having the same issue, as described in the first "XCP-ng 8.2.1 thread":

                            fcoe_driver CRITICAL: ['Traceback (most recent call last):\n', '  File "/opt/xensource/libexec/fcoe_driver", line 34, in execute\n    output = subprocess.check_output(cmd)\n', '  File "/usr/lib64/python2.7/subprocess.py", line 575, in check_output\n    raise CalledProcessError(retcode, cmd, output=output)\n', "CalledProcessError: Command '['fcoeadm', '-i']' returned non-zero exit status 2\n"]
                            

                            8.2.1 is installed and fully patched.
                            Do you have any idea on how to fix this?

                            Best wishes

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

                              @KPS Hi. This thread is now inactive sop please open a new thread dedicated to your issue.

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