MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled)
-
Re: Getting MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled) with XenServer 7.1
We had had this issue in early August then updated our XOAs to resolve it. Ran an update this morning and now my XOA is having this problem again.
• Start time: Monday, October 7th 2024, 2:04:43 pm
• End time: Monday, October 7th 2024, 2:07:57 pm
• Duration: 3 minutes
• Error: MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled) -
@olivierlambert we were using the 'stable' channel. Support had me switch to the 'latest' channel now. That looks like it may have resolved it. My backups are running now will report back once it is completed.
-
Hi,
There's a PR in draft that should fix it once for all: https://github.com/vatesfr/xen-orchestra/pull/8038
-
@olivierlambert Any updates on this? Our backups are still not working. Is there a way to rollback this update where this function is working?
Thanks.
-
If you have a subscription, I would suggest to open a ticket. If you don't, then just wait for the PR to be merged and update again.
-
@olivierlambert Thanks. I opened a support ticket Ticket#7730113.
-
@olivierlambert FYI, I ran the latest XOA updates today and it broke again after it was patched. I have re-opened the existing ticket.
-
Are you on latest? I mean, "latest" channel.
-
@olivierlambert we were using the 'stable' channel. Support had me switch to the 'latest' channel now. That looks like it may have resolved it. My backups are running now will report back once it is completed.
-
Great news! Indeed,
latest
is shipped with the latest release (ie the one from Halloween/October) while stable is updated to the September release. Since the fix was done only in the last release, this explains the resultAnyway, what you can do on November the 30th, is to switch back to "stable", which be the exact same release than your current "latest".
-
-
-
@olivierlambert Confirmed that the backup completed successfully using the 'latest' channel. Thanks again!
-
Excellent Happy to see our fix solved your problem and enhanced our compatibility with older XenServer version. Don't forget to upgrade, the path to get to XCP-ng is relatively straightforward