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 also deleting by it if the ringX_addr
is set to an IP, else this may be confusing as the user uses
normally the node name only to do things.

Signed-off-by: Thomas Lamprecht <>

This is a follow up patch for the recently pushed commits
which patch set I overlooked on the mailing list

 data/PVE/CLI/ | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/data/PVE/CLI/ b/data/PVE/CLI/
index b26a1ec..b72fb00 100755
--- a/data/PVE/CLI/
+++ b/data/PVE/CLI/
@@ -414,9 +414,11 @@ __PACKAGE__->register_method ({
        foreach my $tmp_node (keys %$nodelist) {
            my $d = $nodelist->{$tmp_node};
+           my $name = $d->{name};
            my $ring0_addr = $d->{ring0_addr};
            my $ring1_addr = $d->{ring1_addr};
            if (($tmp_node eq $param->{node}) ||
+               (defined($name) && ($name eq $param->{node})) ||
                (defined($ring0_addr) && ($ring0_addr eq $param->{node})) ||
                (defined($ring1_addr) && ($ring1_addr eq $param->{node}))) {
                $node = $tmp_node;

pve-devel mailing list

Reply via email to