You could at least send the backup reports (requires backup-reports and transport-email plugin on XOA) to a Microsoft Teams channel of your choice (Channel - More options - Get email adress).

@stormi Did not even know the problem existed . Anyway, added a new (second) DNS server (9.9.9.9) to the DNS server list via xsconsole and rebooted the host (XCP-ng 8.2.0 fully patched).

Before update: DNS 9.9.9.9 did not persist, only the previous settings are shown
After update: DNS 9.9.9.9 did persist the reboot and is listed together with the previous settings

Deleting DNS 9.9.9.9 worked as well, so the xsconsole update worked for me.

@stormi Updated my two host playlab (8.2.0 fully patched, the third host currently serves as a Covid-19 homeoffice workstation) with no error. Rebooted and ran the usual tests (create, live migrate, copy and delete a linux and a windows 10 VM as well as create / revert snapshot (with/without ram) ). Fooled myself with a VM_LACKS_FEATURE error on the windows 10 VM until I realized that I forgot to install the Guest tools - I need more sleep. Will try a restore after tonights backup.

Edit: restore from backup worked as well

Upgraded a three host homelab from XCP-ng 8.1 fully patched to XCP-ng 8.2 beta.
Things done/tested successfully:

• Upgrade process (via ISO)
• Copy/Move of VMs (even cross pool)
• Create/Change VMs (Linux, Windows (but not UEFI))
• Add/remove server to XO from source
• Create/Change networks
• Fresh install process (via ISO)
• Basic storage benchmark on dom0 and Debian VM using fio
• Add, Remove, Re-add NFS shares (ISO and storage)

This weekend I try to do some backup/restore (if time permits).
Nice work XCP-ng rocks

[edit: some more tests]

@stormi Successfully updated my two host playlab (8.2.0 full patched, but with the new guest tools ISO). Rebooted both hosts and ran my usual test program (create, live migrate (without (only Debian) and with guest-tools installed (Debian 10 and Windows 10) avoiding the VM_LACKS_FEATURE error on Windows 10 - more sleep this time ), copy and delete as well as create / revert to snapshot (with/without ram) and (live/halted=shutdown) storage migration remote to local SR and back). Also restored a Debian 10 VM from a pre-update backup with no problem. Looks good . Will see how backup runs tonight, but I am confident that this will work as well.

Edit #1: typos

Edit #2: Thanks to Xen Orchestra, out-of-band management even for Optiplex 9010s, a notebook and a very nice evening on the balcony, I extended my tests to Ubuntu 20 LTS. And you might guess it - works as well

Edit #3: Deleted a subsequent post on an asyncMap is not defined error because it is not related to the security update.

@olivierlambert It is a pleasure to help. I highly appreciate your teams work on making XCP-ng better and more secure as well as the support you give.

@stormi Just did a quick test before and after installing the patch you supplied on one of my playlab hosts (XCP-ng 8.2 fully patched).

Before sudoedit -s '\' `perl -e 'print "A" x 65536'` result in

*** Error in `sudoedit': free(): invalid next size (fast): 0x00005633b9d5b130 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81499)[0x7efdaf3f2499]
/lib64/libc.so.6(__vasprintf_chk+0x144)[0x7efdaf489114]
/lib64/libc.so.6(__asprintf_chk+0x82)[0x7efdaf488fc2]
/lib64/libpam.so.0(+0x4ec1)[0x7efda7ec7ec1]
/lib64/libpam.so.0(+0x5c83)[0x7efda7ec8c83]
/lib64/libpam.so.0(+0x5b62)[0x7efda7ec8b62]
/lib64/libpam.so.0(+0x6235)[0x7efda7ec9235]
/lib64/libpam.so.0(pam_start+0x20b)[0x7efda7ecaa4b]
/usr/libexec/sudo/sudoers.so(+0x8e88)[0x7efda835be88]
/usr/libexec/sudo/sudoers.so(+0x7d61)[0x7efda835ad61]
/usr/libexec/sudo/sudoers.so(+0x9f44)[0x7efda835cf44]
/usr/libexec/sudo/sudoers.so(+0x1d04d)[0x7efda837004d]
/usr/libexec/sudo/sudoers.so(+0x16c84)[0x7efda8369c84]
sudoedit(+0x543f)[0x5633b924e43f]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7efdaf393445]
sudoedit(+0x6d8f)[0x5633b924fd8f]
[...]

With patch applied, result is

usage: sudoedit [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-T timeout] [-u user] file ...

Same goes for sudoedit -s / (did not record before / after), so the patch gives the expected results as described in the linked articels. Already see the respective patches on my Debian VMs as well. Thumbs up for swift reaction

@stormi Can not speak for the issue solved, but upgrading my three host playlab from XCP-ng 8.2 fully patched worked as well as create, live / storage migrate, copy, delete, snapshot (with/without ram), backup and restore of Linux and Windows 10 VMs. Nice upstream, downstream and forum work .

@stormi thank you as well for regulary pushing out security updates and bugfixes . Makes me feel comfortable to have a solid virtualization environment (even with a non-commercial homelab) .

Upgraded a three host homelab:

• ISO upgrade from XCP-ng 8.1 fully patched to XCP-ng 8.2.0 RC
• ISO upgrade from XCP-ng 8.2.0 beta fully patched to XCP-ng 8.2.0 RC
• ISO fresh install of XCP-ng 8.2.0 RC

My quick-and-dirty setup of Let's Encrypt on one of the hosts survived the ISO upgrade - nice

Did a yum update on all hosts and tested:

• Add/remove hosts to XO from source
• Join/remove hosts to a pool.
• Copy/Move of VMs (within and across pools)
• Move VDI between local/shared SR
• Create/Change VMs (Linux, Windows (but not UEFI))
• Add, Remove, Re-add NFS shares (ISO and storage)

@averagecdn Good to know it is working now Have fun with XOA and XCP-ng.

@averagecdn But a ping xoa.io does work?

@averagecdn Did you try to deploy XOA through the CLI? SSH into your XCP-ng host and do a bash -c "$(curl -s http://xoa.io/deploy)". This will download and install the VM.

While "data": ["Not_found"] does not suggest a firewall problem, it is still worth checking if the outgoing port tcp/8888 is open for your XCP-ng host to reach the deployment server (via this port).

@magtech If you want to do a XOA quick deploy, you need a working internet connecting and outbound port tcp/8888 must be open to the internet. New install of XCP-ng, can't complete Quick Deploy might help?

@leiwis-0 Ok! Borzel mantém o XCP Center. Talvez ele possa ajudar a entender o que está acontecendo se a reinicialização não funcionar.

@leiwis-0 Pra ser sincero, nunca tive essa situação, só sei a explicação. De acordo com a documentação, remover o arquivo deve ser suficiente. Reiniciar a pilha de ferramentas ou o servidor ajuda, se isso for possível? Talvez alguém possa ajudar se você perguntar em inglês. Sou um cara que fala alemão e uso o inglês para traduzir para o português

@leiwis-0 Com a ajuda do google tradutor . Isso provavelmente está relacionado ao arquivo de despejo de travamento do servidor naquele host. Não acho que tenha relação com a licença. Consulte a explicação do ícone de status do recurso para o XenCenter. Espero que a tradução funcione

@julien-f yes, works well (even with the 3td party script ). Nice job and fast as usual . Thanks @Alexander-0 for helping to pin it down

@olivierlambert Could need some help on testing this, since I am not sure if that was the correct way.

First did a Xen Orchestra Appliance (XOA) quick deploy on my playlab master host and registered XOA. Only telemetry (v0.4.0) and xoa (v0.11.3) are available plugins after deployment, both active. Logged in via SSH and did a sudo xoa-updater --upgrade which updated XOA successully.

Since the the transport-email plugin was not available/installed after the quick deploy, I installed it manually - is that the correct way do install a plugin on XOA ? npm complained but installed the plugin:

[17:35 05] xoa@xoa:~$ sudo npm install --global xo-server-transport-email
npm WARN deprecated xo-server-transport-email@0.5.0: Dont install XO plugin from npm, please refer to documentation https://xen-orchestra.com/docs/from_the_sources.html
+ xo-server-transport-email@0.5.0
added 6 packages from 3 contributors in 1.136s

And after a sudo systemctl restart xo-server.service the plugin transport-email (v0.5.0) is now available in XOA under settings/plugins. The plugin can be configured (settings can be saved), activated and it tests successfully. So transport-email (v0.5.0) on XOA does work, while transport-email (v0.6.0) on XO from 3rd party script does not.

@meth0d Same here. Since I use a third party script by Jarl01 on Github, I opened an issue over there first, pinging @DustinB who is the maintainer.

Edit: Link to the issue on Github https://github.com/Jarli01/xenorchestra_updater/issues/39

gskger created this issue in Jarli01/xenorchestra_updater

closed Plugin transport-email (v0.6.0) not working #39