Unassigned job IDs

[smashwilson]

Bizarrely, it seems that sometimes, the POST /jobs call can return a response that doesn't contain a job ID, even when no errors are reported in the logs or the API. The JobSubmitHandler should never return without assigning an ID to each job.

[rgbkrk]

Even after completely refreshing my system and tossing the loose volumes I had laying around from not using fig rm -v, I was still seeing this last night.

What was this about setting Mongo modes?

[smashwilson]

You can set the mode of your Mongo connection to ensure various degrees of consistency: Strong, Monotonic, or Eventual. Now that I'm thinking about this again, though, I'm not sure that that's it. Read through the JobSubmitHandler function that I linked up above... I'm not seeing how we can reach the end of that without having a jid assigned for each submitted job, without producing an error. Am I missing something obvious?

[rgbkrk]

Thus far I have been unable to reproduce this bug unless I'm using Rackspace's auth store.