At this stage of the Init, config (at least container's) is not done
initializing yet. This makes it impossible for that method to check if
being a slave or not. As a consequence, never fail upon OrmException,
but still issue a corresponding warning in both the console and log.
Slaves usually likely integrate a read-only database, which then lends
such an OrmException upon trying to upgrade their schema. If failing to
upgrade in another context or for another reason, then the admin can
otherwise advise based on the issued warning.
Bug: Issue 11016
Change-Id: I9816142cc1343f9734850d75c9b9ff64cccd99e9
88cb135736