wipe_corosync_state leaves corosync in a state where it cannot upgrade

[Adam Dyess]

While performing an upgrade of corosync on a machine where pacemaker_remote is installed, corosync could not upgrade because of a missing config file.

Perhaps in addition to wipe_corosync_state, you should also mask the corosync service if its not intended to be run

Setting up corosync (2.4.3-0ubuntu1.2) ...
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
invoke-rc.d: initscript corosync, action "restart" failed.
● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-09-01 13:31:15 UTC; 6ms ago
     Docs: man:corosync
           man:corosync.conf
           man:corosync_overview
  Process: 1515356 ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS (code=exited, status=8)
 Main PID: 1515356 (code=exited, status=8)

Sep 01 13:31:15 compute-server-1 systemd[1]: Starting Corosync Cluster Engine...
Sep 01 13:31:15 compute-server-1 corosync[1515356]: Can't read file /etc/corosync/corosync.conf reason = (No such file or directory)
Sep 01 13:31:15 compute-server-1 corosync[1515356]: Can't read file /etc/corosync/corosync.conf reason = (No such file or directory)
Sep 01 13:31:15 compute-server-1 systemd[1]: corosync.service: Main process exited, code=exited, status=8/n/a
Sep 01 13:31:15 compute-server-1 systemd[1]: corosync.service: Failed with result 'exit-code'.
Sep 01 13:31:15 compute-server-1 systemd[1]: Failed to start Corosync Cluster Engine.

[Adam Dyess (addyess)]

as a workaround for package upgrades:

```bash
sudo systemctl mask corosync
sudo dpkg --configure -a
```

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-pacemaker-remote/+/815611

[OpenStack Infra (hudson-openstack)]

Change abandoned by "James Page <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-pacemaker-remote/+/815611
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Jadon Naas (jadonn)]

This change was abandoned a year ago after a significant period of time without any comment. Is the reported behavior in the bug still an issue for anyone at this time?