The use of AtomicUpdate by genericetcd doesn't handle conflicting writes by rejecting that to a user. It should.

Eventually, we may want to hide write conflicts to /pods when status has changed, and to spec when /pods/status changes, but that requires us to have two version counters and that's not worth the effort.

Fix incoming.