When an unsupecting user clones and then builds the nodemanager repo, the startling result is a non-working nodemanager which doesn't even try to educate the user about what's wrong.
For example, if the seattleinstaller was never run, critical bits of information are missing from the nodeman.cfg, and nmmain.py's overly optimistic attempt to find them result in opaque errors in the nodemanager log such as
1518746365.41:PID-5676:[INFO]:Loading config
1518746365.42:PID-5676:Traceback (most recent call last):
File "nmmain.py", line 775, in <module>
File "nmmain.py", line 581, in main
KeyError: 'publickey'
(By the way, the missing key here is the node's RSA key, not a vessel user/owner key.)
Thanks go out to Bryan Boyd for reporting this issue!
When an unsupecting user clones and then builds the
nodemanagerrepo, the startling result is a non-working nodemanager which doesn't even try to educate the user about what's wrong.For example, if the
seattleinstallerwas never run, critical bits of information are missing from thenodeman.cfg, andnmmain.py's overly optimistic attempt to find them result in opaque errors in the nodemanager log such as(By the way, the missing key here is the node's RSA key, not a vessel user/owner key.)
Thanks go out to Bryan Boyd for reporting this issue!