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 approach. On Nov 11, 2014 11:52 PM, "Michael Rasmussen" <m...@datanom.net> wrote:
> On Wed, 12 Nov 2014 05:36:40 +0000 > 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 filesystem since we block > remount > > > as our current directory is the mount point for pve filesystem. > > > > Sure, you cannot do that if you current directory is inside /etc/pve. > The solution is > > to change to another directory, for example > > > > # cd > > # pvecm add ... > > > > > > > I know this but when changes for failure is 100% the command should > warn the user and refuse to continue. > > -- > Hilsen/Regards > Michael Rasmussen > > Get my public GnuPG keys: > michael <at> rasmussen <dot> cc > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E > mir <at> datanom <dot> net > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C > mir <at> miras <dot> org > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 > -------------------------------------------------------------- > /usr/games/fortune -es says: > The IBM 2250 is impressive ... > if you compare it with a system selling for a tenth its price. > -- D. Cohen > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > >
_______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
