Closed
Bug 1124388
Opened 9 years ago
Closed 7 years ago
improve aws_deploy_cloudstack's logging, handling of rollbacks
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dustin, Unassigned)
Details
First, when a stack is created and ends in status ROLLBACK_COMPLETE, it can't be updated and must be deleted. aws_deploy_cloudstack should do this automatically. Second, AWS's supply of "events" related to a stack sucks. It just gives you a list of ALL events, with no way to filter out those which occurred before a particular time. There's some code in place to try to fix this, but it doesn't seem to work -- when you update a stack, you still see a huge spew of events for previous create/update operations.
Reporter | ||
Comment 1•9 years ago
|
||
https://github.com/mozilla/build-cloud-tools/pull/18 solves the second item.
Reporter | ||
Updated•9 years ago
|
Assignee: dustin → nobody
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•