There may be a problem with the following situation:
Server A and Server B know each other.
Start a reinstallation of server B from server A.
During the installation a go-susi client is running on server B (from the NFSroot) and potentially there is an attempt to start another go-susi when the go-susi package is being installed. Because server A has server B still listed as a peer in its serverdb, it will attempt to communicate with it as a server. Also if go-susi is (re)started on server B it will register at itself which makes server A lose server B as a client (for purposes of savelog and progress bar).
Examine the above situation in detail and check for bugs.
From mux2...@gmail.com on November 15, 2013 15:08:01
There may be a problem with the following situation:
Server A and Server B know each other.
Start a reinstallation of server B from server A.
During the installation a go-susi client is running on server B (from the NFSroot) and potentially there is an attempt to start another go-susi when the go-susi package is being installed. Because server A has server B still listed as a peer in its serverdb, it will attempt to communicate with it as a server. Also if go-susi is (re)started on server B it will register at itself which makes server A lose server B as a client (for purposes of savelog and progress bar).
Examine the above situation in detail and check for bugs.
Original issue: http://code.google.com/p/go-susi/issues/detail?id=163