yahoo-eng-team team mailing list archive

[OpenStack Infra <1599296@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/409010
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=34f1201a2f1250d77ca21c51e89c2edd313c8597
Submitter: Jenkins
Branch:    master

commit 34f1201a2f1250d77ca21c51e89c2edd313c8597
Author: “Richard <csravelar@xxxxxxxxx>
Date:   Fri Dec 9 08:13:15 2016 +0000

    Add id to conflict error if caused by duplicate id
    
    This patch adds test coverage for duplicate erros on objects that
    would raise an exception conflict by duplicate ids. It also adds
    the id of the object in place of the name in the duplicate error
    message if a name field for the object cannot be found.
    
    Closes-Bug: #1599296
    
    Change-Id: Ief9ef3d29ee9ac2da1c205247601399fb6f79d7b


** Changed in: keystone
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1599296

Title:
  exception.Conflict does not give specifics

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  When attempting to create a duplicate entity, the exception raised
  only provides the resource type that was involved in the request [0].
  It would be nice to know exactly what caused the unique constraint to
  fail. Many deployers are creating multiple keystone objects
  simultaneously, and so it can get confusing when trying to decipher
  what error goes with what object that was trying to be created.

  
  [0] http://cdn.pasteraw.com/dh2hbk5m6hkhagpbjog07ve2ud1z71j

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1599296/+subscriptions