Trove errors displayed with double period '..'

[Andrew Bramley]

Some trove exceptions wrap other exception messages e.g. GuestError, TaskManagerError wrap something like:

class GuestError(TroveError):

    message = _("An error occurred communicating with the guest: "
                "%(original_message)s.")

The 'original_message' is correctly formatted and ends in a period - therefore once wrapped you end up with double period in these error messages e.g.

ERROR: An error occurred communicating with the guest: The 'list_users' operation is not supported for the 'mongodb' datastore..

We should remove the period at the end of GuestError and TaskManagerError exceptions

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Nikhil Manchanda (<email address hidden>) on branch: master
Review: https://review.openstack.org/142759
Reason: Abandoning changes that are greater than 1 month old with a negative
review (and no new patchsets) as part of a regular clean up of
reviews. Please feel free to restore your change if this is still work
in progress.

[Amrith Kumar (amrith)]

These have (mostly) been fixed. Without a specific example of where this is still the case, I'm going to let this expire in 60 days.

[Launchpad Janitor (janitor)]

[Expired for OpenStack DBaaS (Trove) because there has been no activity for 60 days.]