(bug 45366) CentralNotice using wrong DB for logging

CentralNotice was not correctly querying the master DB when performing
logging operations. Instead it was querying the slave which could
result in dblag related issues.  Always query the master to get id.

Additionally -- this patch fixes bugs wrt translation when using the
newly refactored code.

Change-Id: I49a53304ca8352bb62a21873274fc42331a60bdd