From 008f8e22ae33b9b128e79243c000b733ee88cd44 Mon Sep 17 00:00:00 2001 From: Jarrod Johnson Date: Thu, 12 Apr 2018 15:45:07 -0400 Subject: [PATCH] Abort traversing gap in SMM chain Once there is a gap, the next hop in the chain will be ambiguous. Discovery must always precede from the front-most chassis. --- confluent_server/confluent/discovery/core.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/confluent_server/confluent/discovery/core.py b/confluent_server/confluent/discovery/core.py index 0b7523a2..eb5aea26 100644 --- a/confluent_server/confluent/discovery/core.py +++ b/confluent_server/confluent/discovery/core.py @@ -695,6 +695,9 @@ def get_chained_smm_name(nodename, cfg, handler, nl=None, checkswitch=True): smmaddr = cd[nodename]['hardwaremanagement.manager']['value'] pkey = cd[nodename].get('pubkeys.tls_hardwaremanager', {}).get( 'value', None) + if not pkey: + # We cannot continue through a break in the chain + return None, False if pkey: cv = util.TLSCertVerifier( cfg, nodename, 'pubkeys.tls_hardwaremanager').verify_cert