exception.BadRequest is raised with incorrectly logged message.

[Sushil Kumar]

exception.BadRequest is called with incorrect log messages in two instances.

1. trove/guestagent/datastore/mysql/service.py defines a method MySqlAdmin._get_user is raising exception.BadRequest with incorrect message, for which the correct message does not gets displayed when exception is raised, the exception message displayed is the default message of BadRequest.

2. Another such instance is in trove/instance/models.py Instance.resize_volume._resize_resources.
There is a need to correct that log message, so that it correct messages comes to user-screen.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/64338

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/64338
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=3b6aebe0c5d602fab7913bdde450d87ea3ceab76
Submitter: Jenkins
Branch: master

commit 3b6aebe0c5d602fab7913bdde450d87ea3ceab76
Author: Sushil Kumar <email address hidden>
Date: Sat Dec 28 16:22:22 2013 +0000

    Adds Missing _() for Exception Message Translation

    Reasons:
    - Exception messages missing underscores. This is necessary to
      mark messages as ready for translation, and is already the
      defacto standard across the trove codebase,as per,
      https://wiki.openstack.org/wiki/Translations
    - Because of incorrect Exception messages, it does not overrides
      the default message of BadRequest.

    Changes:
    - Adds the missing underscore function to wrap a few user-facing
      exception messages.

    Change-Id: Ib4a183f717146493e514b8169679a57cc2ecfd01
    Closes-Bug: #1264688