From 78eb44266cfc3e5053b71c27df7b7030641dbf53 Mon Sep 17 00:00:00 2001 From: yangweiwei Date: Fri, 2 Jun 2017 09:53:10 +0800 Subject: [PATCH] Update DirectMappingError in keystone.exception When the correct IndexError happens in federation mapping rule, '{0}' is in a local section, but the value in direct_maps is null. Now I have set insecure_debug to 'True', and it shows like '... (e.g. {0} in a local section).'. But it still shows 'An unexpected...'. Change-Id: If6263229b153828ffa07ee3ad6004f3db7cdfd98 Closes-Bug: #1695131 --- keystone/exception.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/keystone/exception.py b/keystone/exception.py index 2a52cfbd48..b5cbea1a01 100644 --- a/keystone/exception.py +++ b/keystone/exception.py @@ -514,9 +514,9 @@ class MetadataFileError(UnexpectedError): class DirectMappingError(UnexpectedError): - message_format = _("Local section in mapping %(mapping_id)s refers to a " - "remote match that doesn't exist " - "(e.g. {0} in a local section).") + debug_message_format = _("Local section in mapping %(mapping_id)s refers " + "to a remote match that doesn't exist " + "(e.g. {0} in a local section).") class AssignmentTypeCalculationError(UnexpectedError):