<![CDATA[XCP-ng 8.2.1 (maintenance update) - final testing sprint]]>I'm creating this new thread that is the direct sequel to the previous 8.2.1 testing thread, to make it easier to start for anyone coming here from the blog to help.

XCP-ng 8.2.1 is about one last week of community testing from release. We need your help to make it happen.

What is XCP-ng 8.2.1?

It's just an update to XCP-ng 8.2. It's bigger than previous security or bugfix updates we released, but it's the same principle: a maintenance update. Once released, people running XCP-ng 8.2 will just update their hosts as usual.

Then why is it numbered 8.2.1?

Two reasons:

  • Among other changes, we included those from Citrix Hypervisor CU1, and the official version number changed to 8.2.1 there. You will see 8.2.1 instead of 8.2.0 as the minor version number in xsconsole, for example. But in the end it will just be an up to date 8.2 LTS.
  • At the same time as we will release updates for XCP-ng 8.2, we will release new installation ISOs that contain all the updated packages up to now. And also use it as an opportunity to fix a few bugs in the installer (anyone got stuck on the blue installation screen after choosing software RAID with 8.2 installation ISOs? 😅). So in a way, it's also a new release that deserves its own patch version number.

Is it an optional update, like Citrix Hypervisor 8.2 CU1 is?

No. Once released, it will be just another update to XCP-ng 8.2.

Are there new fancy features?

Well, it's a maintenance release so don't expect too much.

However:

  • Secure boot for VMs is now supported (full documentation here. Read it, really: there's a pool configuration step necessary if you want to enable secure boot). Some of you already tested this feature months ago. Now it's time for it to reach everyone. There's a but: XCP-ng's guest tools are not signed with a recent enough certificate and Microsoft's user support is so bad that we haven't been able to get a new signing certificate in months (there are issues with their own website that they have trouble finding a workaround for)! So for now the basic rule is: if you want to enable Secure Boot on a Windows VM, use the signed guest tools from Citrix.
  • The installation of Microsoft's infamous KB4535680 update is now fixed.
  • A few components like qemu are updated to pave the way to future vTPM support. I said future. It's not available yet.
  • Rocket Lake processors are now supported.

Other notable changes

  • Guest template for Windows Server 2022 added.
  • Log rotation. Log files should now be automatically rotated if they reach a size of 100M, without waiting for the daily log rotation. This will better handle the situations where a single log file grows up very fast to the point of filling the log partition.
  • Updated default drivers on the system:
    • avago-mpt3sas-33.100.00.01
    • intel-ice-1.6.4 (new vendor driver RPM. We were previously using the built-in driver from kernel 4.19)
    • intel-ixgbe-5.9.4
    • qlogic-fastlinq-8.42.10.0
    • qlogic-netxtreme2-7.14.76
    • r8125-module-9.003.05 added for some Realtek NICs (might be removed from the final release if we can't get enough feedback)
    • igc-module-4.20.17 added for Intel i225 NICs (might be removed from the final release if we can't get enough feedback or can't fix the remaining issues)
  • The default console menu, xsconsole, was updated and includes an improvement that we had contributed upstream: when the XAPI service is unreachable on the host, xsconsole will try to display a useful error message, rather than displaying a misleading message saying that no network was configured.
  • A bug that we discovered and reported upstream regarding the handling of web pages over HTTPS on the host when HTTP support was forbidden has been fixed, so I could finally enforce HTTPS for the host's web page. Any request to get the web page on port 80 will reply with a 403 error.
  • @r1 has updated our alternate kernel to a much more recent maintenance release of kernel.org's 4.19 branch.
  • samba and openssl were updated, which fixes various CVEs. The update to the samba packages pulled several new dependencies such as gnutls, nettle, python-tdb, ...
  • xenserver-transfer-vm was removed.

How to test

Either install or upgrade a host using the test installation ISOs found at https://mirrors.xcp-ng.org/tmp/

Or update an existing XCP-ng 8.2 host:

  • create a file named xcp-ng-staging.repo.
    [xcp-ng-staging]
name=XCP-ng Staging Repository
baseurl=http://mirrors.xcp-ng.org/8/8.2/staging/x86_64/ http://updates.xcp-ng.org/8/8.2/staging/x86_64/
enabled=0
gpgcheck=1
repo_gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng
  • Update: yum update --enablerepo=xcp-ng-staging
  • Usual instructions from https://xcp-ng.org/docs/updates.html still apply

What to test

As usual, anything that you need XCP-ng for.

We also would like you to give special focus to the following items:

  • UEFI VMs, without Secure Boot
  • UEFI VMs, with Secure Boot (check the docs. There's a manual command to run once on the pool, to download and install the certificates from Microsoft.)
  • On Windows installed from a not too recent image (otherwise the test is impossible), installation of update KB4535680, which updates the list of revocated certificates for Secure Boot. Should work without Secure Boot on, but we had reports of failures in this situation so I'm interested in finding a way to reproduce. Should also work with Secure Boot on.
  • Log rotation if you have a way to trigger very verbose logs.
  • The installer (installation, upgrade, backup restore...).
  • Active Directory connectivity, if you know how to make it work
  • The alternate kernel. Having it tested on a large variety of hardware would be good.

How to come back to the main update track after the tests?

You will have nothing to do to turn a host with this test version of X. Just continue updating your hosts normally in the future.

Ready... Test!

And of course, ask anything.

]]>https://xcp-ng.org/forum/topic/5594/xcp-ng-8-2-1-maintenance-update-final-testing-sprintRSS for NodeFri, 15 May 2026 07:34:12 GMTFri, 18 Feb 2022 12:33:16 GMT60<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Mon, 20 Jun 2022 07:33:27 GMT]]>@KPS Hi. This thread is now inactive sop please open a new thread dedicated to your issue.

]]>https://xcp-ng.org/forum/post/50294https://xcp-ng.org/forum/post/50294Mon, 20 Jun 2022 07:33:27 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Sat, 18 Jun 2022 13:20:36 GMT]]>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

]]>https://xcp-ng.org/forum/post/50254https://xcp-ng.org/forum/post/50254Sat, 18 Jun 2022 13:20:36 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 08 Mar 2022 11:01:04 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/47497https://xcp-ng.org/forum/post/47497Tue, 08 Mar 2022 11:01:04 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Mon, 07 Mar 2022 21:54:29 GMT]]>@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 ?

]]>https://xcp-ng.org/forum/post/47491https://xcp-ng.org/forum/post/47491Mon, 07 Mar 2022 21:54:29 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Sun, 06 Mar 2022 19:57:58 GMT]]>@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).
]]>https://xcp-ng.org/forum/post/47461https://xcp-ng.org/forum/post/47461Sun, 06 Mar 2022 19:57:58 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Sun, 06 Mar 2022 19:40:08 GMT]]>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?

]]>https://xcp-ng.org/forum/post/47460https://xcp-ng.org/forum/post/47460Sun, 06 Mar 2022 19:40:08 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Thu, 03 Mar 2022 15:02:48 GMT]]>@apz If you removed the repo file for staging you can just remove the --enablerepo part.

]]>https://xcp-ng.org/forum/post/47369https://xcp-ng.org/forum/post/47369Thu, 03 Mar 2022 15:02:48 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Thu, 03 Mar 2022 14:58:50 GMT]]>@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?

]]>https://xcp-ng.org/forum/post/47368https://xcp-ng.org/forum/post/47368Thu, 03 Mar 2022 14:58:50 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Thu, 03 Mar 2022 14:47:40 GMT]]>@apz It's not related to your issue, but you need to read https://xcp-ng.org/forum/post/47128

]]>https://xcp-ng.org/forum/post/47367https://xcp-ng.org/forum/post/47367Thu, 03 Mar 2022 14:47:40 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Thu, 03 Mar 2022 14:31:17 GMT]]>@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

]]>https://xcp-ng.org/forum/post/47365https://xcp-ng.org/forum/post/47365Thu, 03 Mar 2022 14:31:17 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Thu, 03 Mar 2022 14:08:51 GMT]]>@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?

]]>https://xcp-ng.org/forum/post/47362https://xcp-ng.org/forum/post/47362Thu, 03 Mar 2022 14:08:51 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Wed, 02 Mar 2022 22:01:48 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/47349https://xcp-ng.org/forum/post/47349Wed, 02 Mar 2022 22:01:48 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Wed, 02 Mar 2022 15:40:36 GMT]]>The error message suggests an internal network error message. Does this host have custom iptables rules, or xapi.conf entries?

]]>https://xcp-ng.org/forum/post/47295https://xcp-ng.org/forum/post/47295Wed, 02 Mar 2022 15:40:36 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 18:52:27 GMT]]>@stormi

# yum reinstall guest-templates-json guest-templates-json-data-linux guest-templates-json-data-other guest-templates-json-data-windows

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 guest-templates-json.noarch 0:1.9.6-1.1.xcpng8.2 will be reinstalled
---> Package guest-templates-json-data-linux.noarch 0:1.9.6-1.1.xcpng8.2 will be reinstalled
---> Package guest-templates-json-data-other.noarch 0:1.9.6-1.1.xcpng8.2 will be reinstalled
---> Package guest-templates-json-data-windows.noarch 0:1.9.6-1.1.xcpng8.2 will be reinstalled
--> Finished Dependency Resolution

Dependencies Resolved

==============================================================================================================================================================================================
 Package                                                      Arch                              Version                                       Repository                                 Size
==============================================================================================================================================================================================
Reinstalling:
 guest-templates-json                                         noarch                            1.9.6-1.1.xcpng8.2                            xcp-ng-updates                             29 k
 guest-templates-json-data-linux                              noarch                            1.9.6-1.1.xcpng8.2                            xcp-ng-updates                             17 k
 guest-templates-json-data-other                              noarch                            1.9.6-1.1.xcpng8.2                            xcp-ng-updates                             12 k
 guest-templates-json-data-windows                            noarch                            1.9.6-1.1.xcpng8.2                            xcp-ng-updates                             14 k

Transaction Summary
==============================================================================================================================================================================================
Reinstall  4 Packages

Total download size: 73 k
Installed size: 61 k
Is this ok [y/d/N]: y
Downloading packages:
(1/4): guest-templates-json-1.9.6-1.1.xcpng8.2.noarch.rpm                                                                                                              |  29 kB  00:00:00     
(2/4): guest-templates-json-data-other-1.9.6-1.1.xcpng8.2.noarch.rpm                                                                                                   |  12 kB  00:00:00     
(3/4): guest-templates-json-data-linux-1.9.6-1.1.xcpng8.2.noarch.rpm                                                                                                   |  17 kB  00:00:00     
(4/4): guest-templates-json-data-windows-1.9.6-1.1.xcpng8.2.noarch.rpm                                                                                                 |  14 kB  00:00:00     
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                         110 kB/s |  73 kB  00:00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : guest-templates-json-1.9.6-1.1.xcpng8.2.noarch                                                                                                                             1/4 
  Installing : guest-templates-json-data-other-1.9.6-1.1.xcpng8.2.noarch                                                                                                                  2/4 
  Installing : guest-templates-json-data-windows-1.9.6-1.1.xcpng8.2.noarch                                                                                                                3/4 
  Installing : guest-templates-json-data-linux-1.9.6-1.1.xcpng8.2.noarch                                                                                                                  4/4 
Traceback (most recent call last):
  File "/bin/create-guest-templates", line 17, in <module>
    loader.insert_templates()
  File "/usr/lib/python2.7/site-packages/guesttemplates/loader.py", line 189, in insert_templates
    self._insert_template(i)
  File "/usr/lib/python2.7/site-packages/guesttemplates/loader.py", line 159, in _insert_template
    conn.request("PUT", "/import_metadata?" + params, tar)
  File "/usr/lib64/python2.7/httplib.py", line 1041, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib64/python2.7/httplib.py", line 1075, in _send_request
    self.endheaders(body)
  File "/usr/lib64/python2.7/httplib.py", line 1037, in endheaders
    self._send_output(message_body)
  File "/usr/lib64/python2.7/httplib.py", line 885, in _send_output
    self.send(message_body)
  File "/usr/lib64/python2.7/httplib.py", line 857, in send
    self.sock.sendall(data)
  File "/usr/lib64/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 32] Broken pipe
  Verifying  : guest-templates-json-data-other-1.9.6-1.1.xcpng8.2.noarch                                                                                                                  1/4 
  Verifying  : guest-templates-json-data-windows-1.9.6-1.1.xcpng8.2.noarch                                                                                                                2/4 
  Verifying  : guest-templates-json-data-linux-1.9.6-1.1.xcpng8.2.noarch                                                                                                                  3/4 
  Verifying  : guest-templates-json-1.9.6-1.1.xcpng8.2.noarch                                                                                                                             4/4 

Installed:
  guest-templates-json.noarch 0:1.9.6-1.1.xcpng8.2                guest-templates-json-data-linux.noarch 0:1.9.6-1.1.xcpng8.2   guest-templates-json-data-other.noarch 0:1.9.6-1.1.xcpng8.2  
  guest-templates-json-data-windows.noarch 0:1.9.6-1.1.xcpng8.2  

Complete!
]]>https://xcp-ng.org/forum/post/47262https://xcp-ng.org/forum/post/47262Tue, 01 Mar 2022 18:52:27 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 16:29:39 GMT]]>@apz does it still fail if you reinstall them anyway?

yum reinstall guest-templates-json guest-templates-json-data-linux guest-templates-json-data-other guest-templates-json-data-windows
]]>https://xcp-ng.org/forum/post/47253https://xcp-ng.org/forum/post/47253Tue, 01 Mar 2022 16:29:39 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 15:46:09 GMT]]>@stormi This command did not produce any output, so I assume the packages are fine.

]]>https://xcp-ng.org/forum/post/47252https://xcp-ng.org/forum/post/47252Tue, 01 Mar 2022 15:46:09 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 14:26:36 GMT]]>@apz does rpm -V guest-templates-json guest-templates-json-data-linux guest-templates-json-data-other guest-templates-json-data-windows give any output (it would reveal if there's a corrupted file)?

]]>https://xcp-ng.org/forum/post/47251https://xcp-ng.org/forum/post/47251Tue, 01 Mar 2022 14:26:36 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 10:06:01 GMT]]>@stormi I ran it 5 times in a row. Always after base-windows-8.json.

]]>https://xcp-ng.org/forum/post/47242https://xcp-ng.org/forum/post/47242Tue, 01 Mar 2022 10:06:01 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 10:02:27 GMT]]>@apz If you run it again, does it fail at the exact same place?

]]>https://xcp-ng.org/forum/post/47241https://xcp-ng.org/forum/post/47241Tue, 01 Mar 2022 10:02:27 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 09:59:22 GMT]]>@stormi Result:

# /usr/bin/create-guest-templates-wrapper
Load /usr/share/xapi/vm-templates/windows-server-2012-64bit.json
Load /usr/share/xapi/vm-templates/sled-12-sp4-64bit.json
Load /usr/share/xapi/vm-templates/rhel-8.json
Load /usr/share/xapi/vm-templates/rhel-7.json
Load /usr/share/xapi/vm-templates/oel-8.json
Load /usr/share/xapi/vm-templates/sle-15-64bit.json
Load /usr/share/xapi/vm-templates/debian-9.json
Load /usr/share/xapi/vm-templates/windows-8-64bit.json
Load /usr/share/xapi/vm-templates/sles-12-sp5-64bit.json
Load /usr/share/xapi/vm-templates/base-sle-hvm.json
Load /usr/share/xapi/vm-templates/windows-10-64bit.json
Load /usr/share/xapi/vm-templates/oel-7.json
Load /usr/share/xapi/vm-templates/coreos.json
Load /usr/share/xapi/vm-templates/debian-11.json
Load /usr/share/xapi/vm-templates/windows-server-2012-r2-64bit.json
Load /usr/share/xapi/vm-templates/sles-12-sp3-64bit.json
Load /usr/share/xapi/vm-templates/windows-server-2016-64bit.json
Load /usr/share/xapi/vm-templates/gooroom-2.json
Load /usr/share/xapi/vm-templates/debian-10.json
Load /usr/share/xapi/vm-templates/windows-server-2022-64bit.json
Load /usr/share/xapi/vm-templates/other-install-media.json
Load /usr/share/xapi/vm-templates/base-sle-hvm-64bit.json
Load /usr/share/xapi/vm-templates/base-kylin-7.json
Load /usr/share/xapi/vm-templates/kylin-7.json
Load /usr/share/xapi/vm-templates/debian-8.json
Load /usr/share/xapi/vm-templates/sled-12-sp3-64bit.json
Load /usr/share/xapi/vm-templates/windows-server-2019-64bit.json
Load /usr/share/xapi/vm-templates/centos-7.json
Load /usr/share/xapi/vm-templates/base-windows-uefi.json
Load /usr/share/xapi/vm-templates/sles-12-sp4-64bit.json
Load /usr/share/xapi/vm-templates/sl-7.json
Load /usr/share/xapi/vm-templates/ubuntu-20.04.json
Load /usr/share/xapi/vm-templates/windows-10-32bit.json
Load /usr/share/xapi/vm-templates/ubuntu-16.04.json
Load /usr/share/xapi/vm-templates/rocky-8.json
Load /usr/share/xapi/vm-templates/windows-8-32bit.json
Load /usr/share/xapi/vm-templates/base-hvmlinux.json
Load /usr/share/xapi/vm-templates/almalinux-8.json
Load /usr/share/xapi/vm-templates/base-el-7.json
Load /usr/share/xapi/vm-templates/centos-8.json
Load /usr/share/xapi/vm-templates/base-windows.json
Load /usr/share/xapi/vm-templates/ubuntu-18.04.json
Load /usr/share/xapi/vm-templates/base-windows-8.json
Destroy 1c33af1c-e919-418c-ad45-85d7d6fb604a
Insert 1c33af1c-e919-418c-ad45-85d7d6fb604a
Traceback (most recent call last):
  File "/usr/bin/create-guest-templates", line 17, in <module>
    loader.insert_templates()
  File "/usr/lib/python2.7/site-packages/guesttemplates/loader.py", line 189, in insert_templates
    self._insert_template(i)
  File "/usr/lib/python2.7/site-packages/guesttemplates/loader.py", line 159, in _insert_template
    conn.request("PUT", "/import_metadata?" + params, tar)
  File "/usr/lib64/python2.7/httplib.py", line 1041, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib64/python2.7/httplib.py", line 1075, in _send_request
    self.endheaders(body)
  File "/usr/lib64/python2.7/httplib.py", line 1037, in endheaders
    self._send_output(message_body)
  File "/usr/lib64/python2.7/httplib.py", line 885, in _send_output
    self.send(message_body)
  File "/usr/lib64/python2.7/httplib.py", line 857, in send
    self.sock.sendall(data)
  File "/usr/lib64/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 32] Broken pipe
]]>https://xcp-ng.org/forum/post/47240https://xcp-ng.org/forum/post/47240Tue, 01 Mar 2022 09:59:22 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 09:54:40 GMT]]>@apz Try to re-run the script that failed:

/usr/bin/create-guest-templates-wrapper
]]>https://xcp-ng.org/forum/post/47239https://xcp-ng.org/forum/post/47239Tue, 01 Mar 2022 09:54:40 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 09:39:29 GMT]]>@stormi The affected host has only 2 templates, 2022 Windows and Suse 12.

]]>https://xcp-ng.org/forum/post/47238https://xcp-ng.org/forum/post/47238Tue, 01 Mar 2022 09:39:29 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 09:36:42 GMT]]>@apz The script that deletes then recreates the guest templates when they are updated apparently failed on your host. Are there any missing templates in your template list?

]]>https://xcp-ng.org/forum/post/47237https://xcp-ng.org/forum/post/47237Tue, 01 Mar 2022 09:36:42 GMT<![CDATA[Reply to XCP-ng 8.2.1 (maintenance update) - final testing sprint on Tue, 01 Mar 2022 09:05:23 GMT]]>I upgraded 3 of my homelab hosts, all were up-to-date 8.2's before this update. One of them blurted out this right at the end of the upgrade, but I did not observe any negative consequences yet.

  Cleanup    : wsproxy-1.12.0-2.xcpng8.2.x86_64                                                                                                                                       162/162 
Traceback (most recent call last):
  File "/bin/create-guest-templates", line 17, in <module>
    loader.insert_templates()
  File "/usr/lib/python2.7/site-packages/guesttemplates/loader.py", line 189, in insert_templates
    self._insert_template(i)
  File "/usr/lib/python2.7/site-packages/guesttemplates/loader.py", line 159, in _insert_template
    conn.request("PUT", "/import_metadata?" + params, tar)
  File "/usr/lib64/python2.7/httplib.py", line 1041, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib64/python2.7/httplib.py", line 1075, in _send_request
    self.endheaders(body)
  File "/usr/lib64/python2.7/httplib.py", line 1037, in endheaders
    self._send_output(message_body)
  File "/usr/lib64/python2.7/httplib.py", line 885, in _send_output
    self.send(message_body)
  File "/usr/lib64/python2.7/httplib.py", line 857, in send
    self.sock.sendall(data)
  File "/usr/lib64/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 32] Broken pipe
]]>https://xcp-ng.org/forum/post/47235https://xcp-ng.org/forum/post/47235Tue, 01 Mar 2022 09:05:23 GMT