scaling_policy logs do not report the stack name

Bug #1486497 reported by Kanagaraj Manickam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Confirmed
Low
Kanagaraj Manickam

Bug Description

When multiple stack is created from the same template, it become difficult to find out which stack the scaling_policy is being handled as scaling_policy does not report the logs with stack name. This bug is filed to add stack name in the log statements in the scaling_policy.

sample:
INFO heat.engine.resources.openstack.heat.scaling_policy ... Alarm scaleup_policy, new state alarm

Here scaleup_policy is the name of the scaling_policy which does not reveal the stack name.

Changed in heat:
assignee: nobody → Kanagaraj Manickam (kanagaraj-manickam)
Angus Salkeld (asalkeld)
Changed in heat:
importance: Undecided → Low
status: New → Confirmed
Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.