Oy.  WTF?

ppbrabhu@ - was this related to anything happening during recovery
from trouble last night?

This can happen if some other builder is cycling on updating the manifest repeatedly around the same time...

Looking at the history of the chromeos/manifest-versions (that's the one we couldn't push to), it looks like master got really unlucky -- all the release builders died at the same time due to the InitSDK issue, and the master kept hitting their updates to the repo.
The timing matches up for these commits: https://chrome-internal.googlesource.com/chromeos/manifest-versions/+log/master/?s=c0133e66eec9d7ba7bf1c6d030b91d9de67b53b6

https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/17695
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/17694

For records, Happened again.