Comment 3 for bug 1598946

This most certainly is a bug. Inadvertently running multiple services concurrently shouldn't cause the thing to explode.

No other OpenStack services that I have come across will happily create duplicate services entries on starting, and then balk out.

Why would Watcher not want to be deployed HA?

Creating the initial fixtures should either be separated a part of watcher-db-manage process, or (as the current proposed branch does) be idempotent.