Re: [pve-devel] [PATCH cluster] allow also deleting a node by name when ringX_addr is a IP

2016-09-20 Thread Dietmar Maurer
This is not necessary (see corosync_nodelist) > diff --git a/data/PVE/CLI/pvecm.pm b/data/PVE/CLI/pvecm.pm > index b26a1ec..b72fb00 100755 > --- a/data/PVE/CLI/pvecm.pm > +++ b/data/PVE/CLI/pvecm.pm > @@ -414,9 +414,11 @@ __PACKAGE__->register_method ({ > > foreach my $tmp_node (keys %$nod

Re: [pve-devel] [PATCH cluster] allow also deleting a node by name when ringX_addr is a IP

2016-09-20 Thread Thomas Lamprecht
On 09/20/2016 10:42 AM, Fabian Grünbichler wrote: On Tue, Sep 20, 2016 at 10:17:44AM +0200, Thomas Lamprecht wrote: This is an additional (convenience) fix for the delnode param. As we always have the node name in our config - either the 'name' (preferred) or the 'ring0_addr' property of a nod

Re: [pve-devel] [PATCH cluster] allow also deleting a node by name when ringX_addr is a IP

2016-09-20 Thread Fabian Grünbichler
On Tue, Sep 20, 2016 at 10:17:44AM +0200, Thomas Lamprecht wrote: > This is an additional (convenience) fix for the delnode param. > As we always have the node name in our config - either the 'name' > (preferred) or the 'ring0_addr' property of a node entry in the > corosync.conf holds it - allow a