exception.Conflict does not give specifics
Bug #1599296 reported by
Shawn Berger
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Low
|
Richard |
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.
Changed in keystone: | |
importance: | Undecided → Low |
Changed in keystone: | |
assignee: | nobody → Richard (csravelar) |
summary: |
- Keystone error message for duplicate entries doesn't have enough - information + exception.Conflict does not give specifics |
description: | updated |
tags: | added: sql user-experience |
Changed in keystone: | |
assignee: | Richard (csravelar) → Steve Martinelli (stevemar) |
Changed in keystone: | |
milestone: | none → ocata-2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/337892
Review: https:/