wipe_corosync_state leaves corosync in a state where it cannot upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Pacemaker Remote Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
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_
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/
Active: failed (Result: exit-code) since Wed 2021-09-01 13:31:15 UTC; 6ms ago
Docs: man:corosync
Process: 1515356 ExecStart=
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/
Sep 01 13:31:15 compute-server-1 corosync[1515356]: Can't read file /etc/corosync/
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.
tags: | added: openstack-upgrade |
Changed in charm-pacemaker-remote: | |
status: | In Progress → Triaged |
status: | Triaged → Confirmed |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
as a workaround for package upgrades:
```bash
sudo systemctl mask corosync
sudo dpkg --configure -a
```