Thank you for taking the time to report this bug. In an effort to keep an up-to-date and valid list of bugs to work on, I have reviewed this report to verify it still requires effort and occurs on an Ubuntu release in standard support, and it does not.
I have marked Disco was won't fix as it was EOL in this last January 2020.
AND we're still targeting crmsh tool as the "official" way of setting up PACEMAKER. We are targeting PCS to replace CRMSH in a few releases from now (crmsh is currently back in [main] while PCS is still in [universe]).
With that said I'm considering this bug as fix released since Eoan.
Thank you for taking the time to report this bug. In an effort to keep an up-to-date and valid list of bugs to work on, I have reviewed this report to verify it still requires effort and occurs on an Ubuntu release in standard support, and it does not.
I have marked Disco was won't fix as it was EOL in this last January 2020.
Currently, for focal we have:
- PCS: 0.10.4-2ubuntu1 (Debian: 0.10.4-2, Upstream: 0.10.5)
- COROSYNC: 3.0.3-2ubuntu1 (Debian: 3.0.3-2 +fixes, Upstream: v3.0.3)
- PACEMAKER: 2.0.3-3ubuntu1 (Debian: 2.0.3-3, Upstream: 2.0.3)
AND we're still targeting crmsh tool as the "official" way of setting up PACEMAKER. We are targeting PCS to replace CRMSH in a few releases from now (crmsh is currently back in [main] while PCS is still in [universe]).
With that said I'm considering this bug as fix released since Eoan.