Hi Dietmar,
Found a bug this evening which results in a broken cluster.
Howto replicate bug:
We assume an existing cluster exist on node pve122.
1) Create a fresh proxmox node. Lets call it pve123
2) login to this node as root
3) cd /etc/pve
4) pvecm add pve122
5) initial cluster joining starts
5) initial cluster joining starts which at some point involves restarting pve-
cluster. when pve-cluster restarts the running initial cluster joining
process halts
since pve-cluster is not able to remount pve filesystem since we block remount
as our current directory is the mount point for
On Wed, 12 Nov 2014 05:36:40 +
Dietmar Maurer diet...@proxmox.com wrote:
5) initial cluster joining starts which at some point involves restarting
pve-
cluster. when pve-cluster restarts the running initial cluster joining
process halts
since pve-cluster is not able to remount pve
We *have* operated largely under the understanding that not all Proxmox
sysadmins will fully understand the process that each command goes through
before they invoke it. A sanity check to ensure the directory can be
manipulated before starting the cluster join would be in keeping with that
