@Danp said in XOA fails after update to 5.106.0:

@Lhoust Thanks for the feedback. The developers will fix the issue with XOA Free ASAP.

Although switching the channel from latest to stable dropped XOA Free down to 5.105, XOA Free remained Expired License LOCKED. Yesterday Quick Deploy was Blocked, therefore I used the Source Code Version to restore my XOA Free 5.105 Backup, which worked normally.

What do you mean by blocked? Was the site down?

The Connection was being "Refused", which might also mean the Server Load was too High?

Today my Restored XOA Free 5.105 shows 5.105 is the "Current" Version, XOA 5.106.1 is NO longer available as an upgrade.

This is accurate if you are on the Stable release channel. v5.106.1 is still available on the Latest release channel.

For me Today, 5.105 is still what is available on the latest channel...

Yesterday upgrading to XOA Free 5.106.1 left me in Expired License LOCK. Although switching the channel from latest to stable dropped XOA Free down to 5.105, XOA Free remained Expired License LOCKED. Yesterday Quick Deploy was Blocked, therefore I used the Source Code Version to restore my XOA Free 5.105 Backup, which worked normally.

Today my Restored XOA Free 5.105 shows 5.105 is the "Current" Version, XOA 5.106.1 is NO longer available as an upgrade. Although Quick Deploy is no longer Blocked, I have not tried that option, making do with the XOA Free 5.105 I restored yesterday, as I wait for the Expired License Issue with XOA Free 5.106.1 to be resolved...

@olivierlambert said in XO (from source): backup error (to Wasabi):

If you need another trial, no problem. To me, the problem is not in XOA (the broken commit was done after the monthly release) and fixed today, so it means it would be never shipped in XOA.

Then I am fine, building XO from Sources provides me with the ability to backup my VMs, which was the only XOA "Feature" I was using...

Thanks anyway!!!

@olivierlambert said in XO (from source): backup error (to Wasabi):

@Lhoust you can always trigger a trial and test on XOA Latest. If you already had a trial, I'll be happy to renew it.

For me Today's XO Build from Sources [Xen Orchestra, commit 21bd7] is working correctly, therefore I have been able move past yesterday's problem and update the Backups of all VMs...

You have already been quite generous and provided me with Two Trials...
If it would be of any benefit to Vates, I would be willing for a Third XOA Trail...

Although for me it appears Vates has already fixed this bug with [Xen Orchestra, commit 21bd7], therefore I should be fine...

@geogak said in XO (from source): backup error (to Wasabi):

@Lhoust try updating to the latest commit, it looks like it was fixed in b62e803.

Here is the github link if youre intrested in then change (I am)
https://github.com/vatesfr/xen-orchestra/commit/b62e8035fca4e8cefcb2d1465d585342c720b45d#diff-7c35aaf9805ed05fd9c00b9a5ab3ac8a82f479d03331f0bc771002e302763a39R275

Yesterday with Xen Orchestra, commit 63a88: I was receiving the Error Message when either attempting to Modify my "Restored" Backup Jobs or trying to re-Create New Backup Jobs

Rolling back to my previous builds from August 30: Xen Orchestra, commit f1780
September 9: Xen Orchestra, commit 6c8d4
and running today's "Current" build Xen Orchestra, commit 21bd7

I have been able to re-Create (and Run) my "Broken" Restored Backup Jobs (which I had deleted yesterday)!

Yesterday I was receiving the same Error Message: XO from Sources with TrueNAS CORE as my Remote [Xen Orchestra, commit 63a88 --- Master, commit 21bd7].

Log also Empty...

NOTE: Yesterday my XCP-ng 8.3 RC2 had stopped responding, therefore had to reinstall, restoring the VMs and XO Config from a August 30th Backups, if that might be relevant?

Backups are a Paid Feature, therefore I am unable to verify whether Backups work under XO...