continuous replication problems

Gheppy

There are problems with continuous replication. It gets stuck and doesn't go any further.
With commit c6451cfa35f651ce55c86d7feba1f8cbbdf6652c everything is ok on all sites.

On connection in the same site, let's say 10.1.60.0/24 all is ok with last commit.

But on the connection between different sites, for example 10.1.60.0/24 the second SR (vrs4) and 10.1.100.0/24 the first SR (vrs1, vrs2) and XOCE ( on vrs1 ) in 10.1.100.0/24

With commit 6c16055a185ba77950e4a7ee510ab2d705751d0c I have this problem

with last commit 8e5d94dd31aafe78cb65c010c7284fdd9308c770 I have this problem

Andrew

@julien-f CR is running again on XO source with Master, commit 583c7...

julien-f

@Gheppy bfb8d3b has introduced a number of issues, but 6c16055 should have fixed most of them, please test and let me know.

Gheppy

same problem as commit 8e5d94dd31aafe78cb65c010c7284fdd9308c770
I removed the proxy for the system and there are no differences.

Tristis Oris

don't looks like commit related issue. my CR works fine before and after 6c16055 fix.

Gheppy

same for me, this commit c6451cfa35f651ce55c86d7feba1f8cbbdf6652c is fine

Andrew

@julien-f @olivierlambert
c6451cfa35f651ce55c86d7feba1f8cbbdf6652c works.
6c16055a185ba77950e4a7ee510ab2d705751d0c causes the failure.

Tristis Oris

not fine, today CR task stuck and run forever.

olivierlambert

I bet on some other undici failures/bugs since we switched to it what do you think @julien-f ?

Gheppy

Testing commit 1d912bddab506d85ff5abbf36ad23cb795715eaf, same problem
To be more clear
This setup works with last commit

This setup is not working, it never ends

julien-f

Yes, this is likely related to the undici changes even though I don't know yet how, I will investigate today.

Andrew

@julien-f @olivierlambert Any update?

JamfoFL

I just wanted to chime in that I was having the same issue after updating to the latest commit earlier today, 1b5157e9a7a7ba9a49ebc9484737c34ef3da95ed.

I rolled back to my previous commit (granted, it's a bit of an older one as I hadn't updated since last week) and the CR backups started working again perfectly.

In my case, both XCP-ng hosts are on the same subnet.

So, something seems to have broken CR backups between last week and today. Fortunately, rolling-back got everything working again.

If there's anything I can do on my end that might help, just let me know!

julien-f

@Andrew I'm still working on this, expect a fix or a rollback during today.

Andrew

@julien-f Giving fix-putResource a quick test, CR works again.

Andrew

@julien-f CR is running again on XO source with Master, commit 583c7...

JamfoFL

@julien-f I can confirm what @Andrew posted... I also updated to Master Commit 583c7 and the CR backups are working properly once again!

Thank you so much!!

Gheppy

And I confirm this, the problem has disappeared.
Thank you