[ClusterLabs] how to properly add/delete qdevice for an existing cluster

Jan Friesse jfriesse at redhat.com
Wed Apr 8 05:13:34 EDT 2020

> please forgive me if i have overlooked the answer somewhere.
> i have an existing cluster that is already configured with a qdevice. i 
> now wish to update that configuration to point at a different qdevice.
> background:
> for the sake of working through the initial configuration details, 
> tuning, etc, i initially spun up a qdevice that lives on the same VM 
> host as one of the member nodes. obviously this is not robust enough for 
> production setup, so i have created a new qdevice elsewhere. now i want 
> to update the existing cluster to point at the new qdevice. re-running 
> corosync-qdevice-net-certutil results in:
> Node <NODE1> seems to be already initialized. Please delete 
> /etc/corosync/qdevice/net/nssdb
> obviously, i could (and possibly must) muck around in 
> /etc/corosync/qdevice/net/nssdb, but i thought i would ask on-list, for 
> the benefit of future googlers, whether there is a proper way to manage 
> the qdevice without blowing away the existing configuration and 
> re-initializing.

You mean different qnetd? If so, then it is enough to update nodes 
config to point to new IP and copy /etc/corosync/qnetd directory to new 
qnetd server and make sure to chown directory to coroqnetd:coroqnetd 
user:group (this gets created dynamically on installation so uid/gid may 
differ between machines).


> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> ClusterLabs home: https://www.clusterlabs.org/

More information about the Users mailing list