Commit 5bba4a30 authored by Jameson Rollins's avatar Jameson Rollins

catch connection errors in worker manager subordinate checking

This was an oversight bug.  Throw connection error, as expected.
parent 9e39fef0
Pipeline #47916 passed with stages
in 4 minutes and 26 seconds
......@@ -447,17 +447,22 @@ class Worker(multiprocessing.Process):
continue
# CHECK MANAGER SUBORDINATES
subnodes_total = set()
subnodes_not_ok = set()
for mngr in self._system.node_managers:
# make sure all nodes are initialized (node.init() is idempotent)
mngr.init()
# count subordinates nodes
subnodes_total |= set(mngr.nodes.keys())
subnodes_not_ok |= mngr.not_ok()
# FIXME: should we be running check_fault() here?
self['SUBNODES_TOTAL'] = len(subnodes_total)
self['SUBNODES_NOT_OK'] = len(subnodes_not_ok)
try:
subnodes_total = set()
subnodes_not_ok = set()
for mngr in self._system.node_managers:
# make sure all nodes are initialized (node.init() is idempotent)
mngr.init()
# count subordinates nodes
subnodes_total |= set(mngr.nodes.keys())
subnodes_not_ok |= mngr.not_ok()
# FIXME: should we be running check_fault() here?
self['SUBNODES_TOTAL'] = len(subnodes_total)
self['SUBNODES_NOT_OK'] = len(subnodes_not_ok)
except EzcaConnectError as e:
self._usernotify("EZCA CONNECTION ERROR: %s" % e)
self['STATUS'] = 'CERROR'
continue
##############################
##############################
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment