<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hello List,</div>
<div> </div>
<div>i have a question about upgrading an Ubuntu 18.04 FailOver System and hope to get some good hints.</div>
<div> </div>
<div>- OS Ubuntu 18.04</div>
<div>- corosync 2.4.3</div>
<div>- pacemaker 1.1.18</div>
<div>- haproxy 1.8.8</div>
<div> </div>
<div>I have a quite simple system. 2 members in a failover-cluster. I have 2 primitives configured, thats an IP and haproxy. both are grouped to have them active on same member. I followed typical webtutorials.</div>
<div><a href="https://zswiki.kreis-gr.de/wiki/doku.php?do=export_code&id=adoc:serv:lnx:ahb&codeblock=56" title="Schnipsel herunterladen">/etc/corosync/corosync.conf</a> is minimalistic https://pastebin.com/tCLrXYrg</div>
<div> </div>
<div>This works without problems for around 4 years.</div>
<div>Now i plan to do an OS Upgrade to Ubuntu 20.04 and reuse my failovermembers. I could also build a new cluster with new Ubuntu 22.04 servers, but i want to try the upgrade first.</div>
<div> </div>
<div>Ubuntu 20.04 would have these versions:</div>
<div>- pacemaker 2.0.3</div>
<div>- corosync 3.0.3</div>
<div>- haproxy 2.0.29</div>
<div> </div>
<div>Version from 18.04 and 20.04 differ considerable. </div>
<div> </div>
<div>I read this document https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Administration/html/upgrading.html</div>
<div>But iam still not sure to use the Rolling (7.2.2) or the Detach and Reattach (7.2.3) way. May be Detach and Reattach is more appropriate to my scenario. </div>
<div>The thing is to get the cluster working after 1 node is upgraded to make sure primitives/services are able to switch to upgraded host.</div>
<div> </div>
<div>Or do you suggest building a new cluster with new servers, because versions from 18.04/20.04 differ to much?</div>
<div> </div>
<div>Thank you,</div>
<div>Hajo</div>
<div> </div>
<div> </div>
<div> </div>
<div class="signature"> </div></div></body></html>