User creation error not descriptive

[Ryan Rossiter]

When the creation of a user fails by some exceptions within Keystone, the error message given by Horizon is "Error: Unable to create user." The error message within Keystone CLI shows detailed description of error.

To replicate:

1. Raise an exception within keystone/keystone/identity/controllers.py by adding this line:

def create_user(...):
    ...

    self.assert_admin(context)

    # Add this line
    raise exception.ValidationTimeStampError()

    ...

2. Restart keystone service

3a. Within CLI:
> keystone user-create --name=example --pass=examplepass --<email address hidden>

Output:
> Timestamp not in expected format. The server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400)

3b. Within Horizon:
Create user with same information as CLI (add to any project and role)

Output:
Error: Unable to create user

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by David Lyle (<email address hidden>) on branch: master
Review: https://review.openstack.org/105232
Reason: No updates since July. If this is still being worked on restore the review and rebase.

[Matt Borland (palecrow)]

I think there needs to be a little more detail in this bug as it doesn't clarify if the problem is due to Keystone not returning enough useful information in its response for Horizon to respond accordingly. Horizon cannot just pass on English errors, it needs distinguishable error indications so it can provide appropriate localization and detail in its error messages. If the problem is that Keystone is providing a unique error code, then it is a Horizon bug; otherwise this is a problem with Keystone not providing enough information.

[Launchpad Janitor (janitor)]

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