Went back to 22.02.2.1 due to kubernetes bug now I don't see replication tasks

[Intel]

I originally installed 22.02.2.1 and a few days ago upgraded to latest. During this time I added some local data sync tasks; since apps stopped working on the latest version (https://ixsystems.atlassian.net/browse/NAS-117623) I just enabled the old version using the System > Boot menu. Now all my 'replication tasks' are empty.

This feels unexpected, shouldn't the boot environment keep my configuration for everything? I shouldn't have lost my replication settings.

Reactivating 22.02.3 version shows them up... Also here's the kubernetes bug:

0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.

 

[danb35]

Now all my 'replication tasks' are empty.

Are these the "local data sync tasks" that you added after you upgraded to .3, or were these things you'd previously had set up under .2.1? If the former, this would seem like expected behavior--AFAIK, the previous boot environment retains the configuration database it had just before the upgrade.

 

[Intel]

Are these the "local data sync tasks" that you added after you upgraded to .3, or were these things you'd previously had set up under .2.1? If the former, this would seem like expected behavior--AFAIK, the previous boot environment retains the configuration database it had just before the upgrade.

Yes, local sync tasks (full-clone pool A to B). I added them after I upgraded them.

I'm really unsure why this 'data protection' setting is bound to the boot-environment and not part of regular configuration :/