Fixes log format bug when alarm action not present
Signed-off-by: diazb <bdiaz@whitestack.com>
Change-Id: I08b8476c2ffc3c89554fe77a11dbaabbd221d071
diff --git a/policy_module/osm_policy_module/core/agent.py b/policy_module/osm_policy_module/core/agent.py
index aa3f3ff..3a3b20c 100644
--- a/policy_module/osm_policy_module/core/agent.py
+++ b/policy_module/osm_policy_module/core/agent.py
@@ -113,7 +113,7 @@
log.info("Sending scaling action message for ns: %s", alarm_id)
lcm_client.scale(alarm.scaling_record.nsr_id, alarm.scaling_record.name, alarm.action)
except ScalingAlarm.DoesNotExist:
- log.info("There is no action configured for alarm %.", alarm_id)
+ log.info("There is no action configured for alarm %s.", alarm_id)
except Exception:
log.exception("Error consuming message: ")