In the midst of testing this behavior on staging I realized that erroring out of kelvinate() was the wrong thing - the user should get notified that something went wrong by the Command giving a CommandError. By the time we get to kelvinate() we should already know that we have a good environment. But since kelvinate() might end up getting called by something else, I left it logging the error to the console and the the celery log, and returning.

Does this seem good to you @sefk?