remote/coordinator: reduce exporter failure details

Avoid including the full resource representation in exporter acquire/release failure messages returned to the client.
The exporter-provided reason is enough for users, while the full resource details can be noisy and may expose more information than needed.

Signed-off-by: Alex Tercete <alex.tercete@arm.com>
Reviewed-by: Alex Tercete <alex.tercete@arm.com> # gatekeeper
Co-authored-by: Idan Saadon <idan.saadon@arm.com>

Author: 2 people

labgrid/remote/coordinator.py

@@ -689,7 +689,7 @@ async def _acquire_resource(self, place, resource):
         except asyncio.TimeoutError as e:
             raise ExporterError("timed out waiting for exporter while acquiring resource") from e
         if not cmd.response.success:
-            raise ExporterError(f"failed to acquire {resource} ({cmd.response.reason})")
+            raise ExporterError(cmd.response.reason or "exporter returned failure without a reason")
         if resource.acquired != place.name:
             logging.warning("resource %s not acquired by this place after acquire request", resource)
 
@@ -789,7 +789,7 @@ async def _release_resources(self, place, resources, callback=True):
                     except asyncio.TimeoutError as e:
                         raise ExporterError("timed out waiting for exporter while releasing resource") from e
                     if not cmd.response.success:
-                        raise ExporterError(f"failed to release {resource} ({cmd.response.reason})")
+                        raise ExporterError(cmd.response.reason or "exporter returned failure without a reason")
                     if resource.acquired:
                         logging.warning("resource %s still acquired after release request", resource)
             except ExporterError as e: