This was resolved in OSP 14 but I guess we need the backport, which is in progress upstream. However, despite appearances, this is not an exception: it's just a warning that has been defined in the 'oslo_db.exception' module for some unknown reason. As such, I don't think this is an issue and the warning can be safely ignored.