python-heatclient

Bug #1242947
Activity log

Activity log for bug #1242947

Date	Who	What changed	Old value	New value	Message
2013-10-21 23:29:13	Chris Friesen	bug			added bug
2013-10-21 23:30:35	Chris Friesen	description	I started up a stack based on "WordPress_Single_Instance_With_HA.template", named "teststack2". I then shut down the httpd service several times in a row to test the HA behaviour. At this point running "heat event-list teststack2" gave the following: cfriesen@ubuntudevstack:~/devstack$ heat event-list teststack2 +------------------------+----+------------------------------+--------------------+----------------------+ \| resource_name \| id \| resource_status_reason \| resource_status \| event_time \| +------------------------+----+------------------------------+--------------------+----------------------+ \| CfnUser \| 69 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:49Z \| \| WaitHandle \| 70 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:49Z \| \| WaitHandle \| 71 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:49Z \| \| CfnUser \| 72 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:49Z \| \| WebServerKeys \| 73 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:49Z \| \| WebServerKeys \| 74 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:50Z \| \| WikiDatabase \| 75 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:50Z \| \| WikiDatabase \| 76 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:55Z \| \| WaitCondition \| 77 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:55Z \| \| WebServerRestartPolicy \| 78 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:55Z \| \| WebServerRestartPolicy \| 79 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:56Z \| \| HttpFailureAlarm \| 80 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:56Z \| \| HttpFailureAlarm \| 81 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:57Z \| \| WaitCondition \| 82 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:27:53Z \| \| WebServerRestartPolicy \| 83 \| alarm state changed to ALARM \| signal_COMPLETE \| 2013-10-21T23:13:54Z \| \| HttpFailureAlarm \| 84 \| state changed \| DELETE_IN_PROGRESS \| 2013-10-21T23:13:54Z \| \| HttpFailureAlarm \| 85 \| state changed \| DELETE_COMPLETE \| 2013-10-21T23:13:54Z \| \| WaitCondition \| 86 \| state changed \| DELETE_IN_PROGRESS \| 2013-10-21T23:13:54Z \| \| WaitCondition \| 87 \| state changed \| DELETE_COMPLETE \| 2013-10-21T23:13:54Z \| I then tried to show the details for event 83, and was successful: cfriesen@ubuntudevstack:~/devstack$ heat event-show teststack2 WebServerRestartPolicy 83 +------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| Property \| Value \| +------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| event_time \| 2013-10-21T23:13:54Z \| \| id \| 83 \| \| links \| http://192.168.2.118:8004/v1/7b3a6ca58cb142e8b48cfc72aa64109d/stacks/teststack2/9a7f581c-3017-4aa0-b3fc-90266f303296/resources/WebServerRestartPolicy/events/83 \| \| \| http://192.168.2.118:8004/v1/7b3a6ca58cb142e8b48cfc72aa64109d/stacks/teststack2/9a7f581c-3017-4aa0-b3fc-90266f303296/resources/WebServerRestartPolicy \| \| \| http://192.168.2.118:8004/v1/7b3a6ca58cb142e8b48cfc72aa64109d/stacks/teststack2/9a7f581c-3017-4aa0-b3fc-90266f303296 \| \| logical_resource_id \| WebServerRestartPolicy \| \| physical_resource_id \| 3de87cf8273c41c8a9c49c491e6c8fc2 \| \| resource_name \| WebServerRestartPolicy \| \| resource_properties \| { \| \| \| "InstanceId": "e6c5a7f0-c1f0-4016-b84c-59f8694437c9" \| \| \| } \| \| resource_status \| signal_COMPLETE \| \| resource_status_reason \| alarm state changed to ALARM \| \| resource_type \| OS::Heat::HARestarter \| +------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+ But when I tried to see the details for event 81, I got a weird error: cfriesen@ubuntudevstack:~/devstack$ heat event-show teststack2 WebServerRestartPolicy 81 Stack not found: teststack2 The stack is still there, other commands work, but for some reason trying to do event-show on some events gives this error.	I'm testing with "master" branch of git devstack running on Ubuntu 12.04. I started up a stack based on "WordPress_Single_Instance_With_HA.template", named "teststack2". I then shut down the httpd service several times in a row to test the HA behaviour. At this point running "heat event-list teststack2" gave the following: cfriesen@ubuntudevstack:~/devstack$ heat event-list teststack2 +------------------------+----+------------------------------+--------------------+----------------------+ \| resource_name \| id \| resource_status_reason \| resource_status \| event_time \| +------------------------+----+------------------------------+--------------------+----------------------+ \| CfnUser \| 69 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:49Z \| \| WaitHandle \| 70 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:49Z \| \| WaitHandle \| 71 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:49Z \| \| CfnUser \| 72 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:49Z \| \| WebServerKeys \| 73 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:49Z \| \| WebServerKeys \| 74 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:50Z \| \| WikiDatabase \| 75 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:50Z \| \| WikiDatabase \| 76 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:55Z \| \| WaitCondition \| 77 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:55Z \| \| WebServerRestartPolicy \| 78 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:55Z \| \| WebServerRestartPolicy \| 79 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:56Z \| \| HttpFailureAlarm \| 80 \| state changed \| CREATE_IN_PROGRESS \| 2013-10-21T22:06:56Z \| \| HttpFailureAlarm \| 81 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:06:57Z \| \| WaitCondition \| 82 \| state changed \| CREATE_COMPLETE \| 2013-10-21T22:27:53Z \| \| WebServerRestartPolicy \| 83 \| alarm state changed to ALARM \| signal_COMPLETE \| 2013-10-21T23:13:54Z \| \| HttpFailureAlarm \| 84 \| state changed \| DELETE_IN_PROGRESS \| 2013-10-21T23:13:54Z \| \| HttpFailureAlarm \| 85 \| state changed \| DELETE_COMPLETE \| 2013-10-21T23:13:54Z \| \| WaitCondition \| 86 \| state changed \| DELETE_IN_PROGRESS \| 2013-10-21T23:13:54Z \| \| WaitCondition \| 87 \| state changed \| DELETE_COMPLETE \| 2013-10-21T23:13:54Z \| I then tried to show the details for event 83, and was successful: cfriesen@ubuntudevstack:~/devstack$ heat event-show teststack2 WebServerRestartPolicy 83 +------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| Property \| Value \| +------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| event_time \| 2013-10-21T23:13:54Z \| \| id \| 83 \| \| links \| http://192.168.2.118:8004/v1/7b3a6ca58cb142e8b48cfc72aa64109d/stacks/teststack2/9a7f581c-3017-4aa0-b3fc-90266f303296/resources/WebServerRestartPolicy/events/83 \| \| \| http://192.168.2.118:8004/v1/7b3a6ca58cb142e8b48cfc72aa64109d/stacks/teststack2/9a7f581c-3017-4aa0-b3fc-90266f303296/resources/WebServerRestartPolicy \| \| \| http://192.168.2.118:8004/v1/7b3a6ca58cb142e8b48cfc72aa64109d/stacks/teststack2/9a7f581c-3017-4aa0-b3fc-90266f303296 \| \| logical_resource_id \| WebServerRestartPolicy \| \| physical_resource_id \| 3de87cf8273c41c8a9c49c491e6c8fc2 \| \| resource_name \| WebServerRestartPolicy \| \| resource_properties \| { \| \| \| "InstanceId": "e6c5a7f0-c1f0-4016-b84c-59f8694437c9" \| \| \| } \| \| resource_status \| signal_COMPLETE \| \| resource_status_reason \| alarm state changed to ALARM \| \| resource_type \| OS::Heat::HARestarter \| +------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+ But when I tried to see the details for event 81, I got a weird error: cfriesen@ubuntudevstack:~/devstack$ heat event-show teststack2 WebServerRestartPolicy 81 Stack not found: teststack2 The stack is still there, other commands work, but for some reason trying to do event-show on some events gives this error.
2013-10-29 04:58:32	Angus Salkeld	heat: status	New	Triaged
2013-10-29 04:58:34	Angus Salkeld	heat: importance	Undecided	Low
2013-10-29 04:58:37	Angus Salkeld	heat: milestone		icehouse-1
2013-10-29 04:58:41	Angus Salkeld	heat: assignee		Angus Salkeld (asalkeld)
2013-10-29 05:05:05	Angus Salkeld	affects	heat	python-heatclient
2013-10-29 05:05:05	Angus Salkeld	python-heatclient: milestone	icehouse-1
2013-10-29 05:12:09	OpenStack Infra	python-heatclient: status	Triaged	In Progress
2013-10-30 23:26:09	OpenStack Infra	python-heatclient: status	In Progress	Fix Committed
2013-12-05 03:53:43	Steve Baker	python-heatclient: milestone		v0.2.6
2014-04-07 22:37:55	Steve Baker	python-heatclient: status	Fix Committed	Fix Released