Comment 2 for bug 1058313

This new problem is similar to but different from the original bug, which was actually about an enlisting node not a commissioning one. They share a cause in that the client requests public-keys without first checking whether that resource actually exists. That didn't seem to break enlistment, but in this case the client apparently errors out when it gets a 404.

I don't believe the fix to this bug caused the new error: it only touched an API view that was specific to enlistment, turning a "Not Found" exception into a 404 HTTP response (so that we wouldn't get a traceaback). The new error happens in a different server-side code path that may simply need a similar fix. Not quite the same one though: it looks as if the client needs an empty success response rather than a 404 if there are no ssh keys.