Activity log for bug #1168154
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2013-04-11 21:13:09 | Madison Scott-Clary | bug | added bug | ||
| 2013-04-12 08:06:08 | Roger Peppe | juju-core: status | New | Confirmed | |
| 2013-04-12 08:06:17 | Roger Peppe | juju-core: importance | Undecided | High | |
| 2013-04-12 14:38:17 | Francesco Banconi | bug | added subscriber Francesco Banconi | ||
| 2013-04-18 09:42:46 | Francesco Banconi | juju-core: status | Confirmed | In Progress | |
| 2013-04-18 09:42:54 | Francesco Banconi | juju-core: status | In Progress | Confirmed | |
| 2013-06-16 00:33:49 | William Reade | juju-core: status | Confirmed | Triaged | |
| 2013-06-16 00:33:53 | William Reade | juju-core: importance | High | Low | |
| 2013-06-16 00:35:48 | William Reade | description | If a service fails to deploy, it cannot be destroyed. To reproduce: 1. Bootstrap 2. Deploy buildbot-master 3. Watch debug-log for install hook failure 4. Destroy buildbot-master | If a service fails to deploy, it cannot be destroyed. To reproduce: 1. Bootstrap 2. Deploy buildbot-master 3. Watch debug-log for install hook failure 4. Destroy buildbot-master This should really be handled with a --force flag for destroy-service, as in lp:1183309 et al, but it could possibly be mitigated as described in the comments. | |
| 2013-10-12 17:17:49 | Curtis Hovey | tags | destroy-service | ||
| 2016-06-17 23:39:29 | Cheryl Jennings | marked as duplicate | 1183309 |
