Nodename 'None' when a download is requested just as a controller is starting up
eposthumus opened this issue · 0 comments
eposthumus commented
If a download is requested very soon after a controller node is restarting for whatever reason, the nodename for the 'other' controller could still be 'None' This would cause a download ticket to be created for a server named 'None_' which will then never finish, the ticket wiill just stay open forever.
Consider hard-coding nodenames so that a controller always knows it's name at startup and does not use the fqdn or hostname.