[pve-devel] [PATCH manager] pve5to6: Make corosync ip/hostname test a warning

Dominic Jäger d.jaeger at proxmox.com
Fri Jul 5 10:32:17 CEST 2019


Hostnames in corosync do work if everything is set up correctly. Thus,
_warning_ users to take care of that is adequate.

Signed-off-by: Dominic Jäger <d.jaeger at proxmox.com>
---
Didn't test this. User "juniper" brought the topic up
https://forum.proxmox.com/threads/proxmox-ve-6-0-beta-released.55670/
and the objection made sense to me.

 PVE/CLI/pve5to6.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PVE/CLI/pve5to6.pm b/PVE/CLI/pve5to6.pm
index b0bd531b..40b5165b 100644
--- a/PVE/CLI/pve5to6.pm
+++ b/PVE/CLI/pve5to6.pm
@@ -371,7 +371,7 @@ sub check_cluster_corosync {
 	    my $key = shift;
 	    my $ring = $entry->{$key};
 	    if (defined($ring) && !PVE::JSONSchema::pve_verify_ip($ring, 1)) {
-		log_fail("$key '$ring' of node '$cs_node' is not an IP address, consider replacing it with the currently resolved IP address.");
+		log_warn("$key '$ring' of node '$cs_node' is not an IP address, consider replacing it with the currently resolved IP address.");
 	    }
 	};
 	$verify_ring_ip->('ring0_addr');
-- 
2.20.1




More information about the pve-devel mailing list