1 mode in cluster 1.8.0r, 1 bucket
upgrade on 2.0.2-769
server is clean and not initialized
I see the same on Linux
Upgrade 1.8.*-> 2.0.2-769 failed
per bug scrub, making this a blocker now.
As far as I can see regression happened in build 2.0.2-758:
One of ns_server changes is critical and quite possible that it affected upgrade path (not necessarily directly):
Apart from massive changes in ns_server there was a couple of patches related to CentOS package:
From my perspective they seem to be harmless.
Also I observe the issue in both online and offline upgrade cases.
I'd love to get any feedback from ns_server team regarding this issue.
Per discussion Aliaksey will take it and I'll take perf regression.