[SOLVED] Corosync.conf is read-only after adding Qdevice

[selfsufficient]

I decided to add a qdevice to my cluster. Turns out that was a mistake. After adding, I started by rebooting a node and it fails to join the cluster again. I figured i could just revert back to a backup corosync file, however it looks like i can no longer modify them at all. I tried stopping corosync on the node that i rebooted but it still doesnt give root any read access. Any ideas on how I can undo my error? Below are the permissions to the file. The error I get when trying to start corosync is that the file is invalid and needs votes defined. In theory if i can revert this file back, the rest should come back online.
-r--r----- 1 root www-data 825 May 3 17:36 corosync.conf

 

[selfsufficient]

Sorry. Immediately after I posted this I realized I needed to stop the cluster on the failed nodes to gain access.
systemctl stop pve-cluster
systemctl stop corosync
pmxcfs -l

Then I could edit the corosync.conf and move it to an exact copy of the original. All is good again.

 

[Stoiko Ivanov]

Thanks for coming back to share how you solved the issue.

Please mark the thread as 'SOLVED' (by clicking on Edit thread above your first post and selecting SOLVED as prefix).

 

[GHverthll]

Thanks for sharing, this took me 2 hours to figure out

 

[SlickNickTX]

Sorry. Immediately after I posted this I realized I needed to stop the cluster on the failed nodes to gain access.
systemctl stop pve-cluster
systemctl stop corosync
pmxcfs -l

Then I could edit the corosync.conf and move it to an exact copy of the original. All is good again.

Thanks for sharing. Running pmxcfs-l is what solved the issue for me. I didn't see this in the official guide.