We use the following check_message in: horizon/exceptions.py openstack_dashboard/dashboards/admin/aggregates/workflows.py openstack_dashboard/dashboards/admin/flavors/workflows.py openstack_dashboard/dashboards/admin/info/tabs.py openstack_dashboard/dashboards/project/cgroups/workflows.py openstack_dashboard/dashboards/project/volume_groups/workflows.py The definition is: 96 def check_message(keywords, message): 197 """Checks an exception for given keywords and raises an error if found. 198 199 It raises a new ``ActionError`` with the desired message if the 200 keywords are found. This allows selective 201 control over API error messages. 202 """ 203 exc_type, exc_value, exc_traceback = sys.exc_info() 204 if set(str(exc_value).split(" ")).issuperset(set(keywords)): 205 exc_value.message = message 206 # NOTE: This function is intended to call inside an except clause. 207 # pylint: disable=misplaced-bare-raise 208 raise 209 The idea would be to deprecate check_message and use exceptions.handle instead.