From 705ff135da86715c7b2f12d3c14b2d45b6630103 Mon Sep 17 00:00:00 2001
From: Lance Bragstad <lbragstad@gmail.com>
Date: Mon, 22 Jan 2018 21:50:22 +0000
Subject: [PATCH] Relay system information in RoleAssignmentNotFound

Since it's possible to have a role assignment on the system now, we
should make sure we handle that case in the RoleAssignmentNotFound
exception

bp system-scope

Change-Id: I2388d65ffa5b68690d9c4f0dd16f16e158f5a091
---
 keystone/exception.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/keystone/exception.py b/keystone/exception.py
index f598769110..55e32acea9 100644
--- a/keystone/exception.py
+++ b/keystone/exception.py
@@ -378,7 +378,7 @@ class DomainSpecificRoleNotWithinIdPDomain(Forbidden):
 class RoleAssignmentNotFound(NotFound):
     message_format = _("Could not find role assignment with role: "
                        "%(role_id)s, user or group: %(actor_id)s, "
-                       "project or domain: %(target_id)s.")
+                       "project, domain, or system: %(target_id)s.")
 
 
 class RegionNotFound(NotFound):