Opened 2 years ago

Closed 2 years ago

Last modified 22 months ago

#1258 closed defect (fixed)

Listing of clusters fails if one host can't be reached

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: major Milestone: Job scheduler extension v1.4
Component: net.sf.basedb.opengrid Keywords:
Cc:

Description

If multiple Open Grid Clusters has been configured and there is a failure when connecting to one of them, the entire listing fails with an error message. For example (if the host is down):

java.net.ConnectException: Connection refused: connect

or (if the fingerprint is not correct):

net.schmizz.sshj.transport.TransportException: [HOST_KEY_NOT_VERIFIABLE] 
Could not verify `ssh-ed25519` host key with fingerprint 
`4d:13:04:30:ba:b0:be:21:62:83:fc:25:07:d6:f1:ca` for `192.168.56.101` on port 22

It would be nice if only the failed cluster was affected and the other remained accessible.

Change History (2)

comment:1 Changed 2 years ago by Nicklas Nordborg

Owner: set to Nicklas Nordborg
Resolution: fixed
Status: newclosed

In 5980:

Fixes #1258: Listing of clusters fails if one host can't be reached

Added an alternate Info() constructor that creates a compatible structure with the connection error information instead of the hostInfo() information.

comment:2 Changed 22 months ago by Nicklas Nordborg

Milestone: Open Grid Scheduler extension v1.4Job scheduler extension v1.4

Milestone renamed

Note: See TracTickets for help on using tickets.