Continuous Replication fails with XO update (June-20)

scot1297tutaio

I am also having issues with Continuous Replication:

️ the writer IncrementalXapiWriter has failed the step writer.checkBaseVdis() with error Cannot destructure property 'other_config' of 'undefined' as it is undefined.. It won't be used anymore in this job execution.
️ Retry the VM backup due to an error
️ the writer IncrementalXapiWriter has failed the step writer.checkBaseVdis() with error Cannot destructure property 'other_config' of 'undefined' as it is undefined.. It won't be used anymore in this job execution.
Error: Cannot destructure property 'other_config' of 'undefined' as it is undefined.

I am on commit a14c4 using XO from sources.

Scot

olivierlambert

@scot1297tutaio please try the branch @florent gave

scot1297tutaio

@olivierlambert I updated to that branch and it is working again. Thank you!

Andrew

@florent @olivierlambert That branch works again for me. No errors any more.

Delgado

I can confirm I upgraded to this branch and replication works again.

olivierlambert

Great news, this is helpful for our dev team, thanks for your feedback! Keep an eye on the PR to see when merged

Andrew

@florent @olivierlambert While this fixes one problem it adds a new one.

I am now getting the error VDI must be free or attached to exactly one VM on more than one VM. Which is correct because the CR process (and also sometimes delta backup) is leaving a VM attached to the Control Domain.

This problem shows up under the Dashboard->Health page. Manually deleting these stuck VDIs resolves the backup issue.

Now that the backup/CR process checks for this condition it becomes more of a problem that the process leaves VDIs attached to the control domain.

So, this update does fix the other_config issue but adds checks for other unrelated problems that exist and need to be resolved (Stuck VDI on Control Domain).

Andrew

@olivierlambert Any updates on this issue?

olivierlambert

Sadly I'm not supervising this part, maybe @julien-f is aware

Andrew

@julien-f @florent I tried the current XO commit 818a5b7f5bf29c021bc1612608c607022bac9c2b and still have the same problems, so I went back to fix_sr_vdi_undefined.

olivierlambert

Got it. We might ship that in a patch release if it's bundled in our tomorrow's latest XOA release.