Posted by anarcat on July 24, 2009 at 2:30am
2 followers
Jump to:
| Project: | Provision |
| Version: | 6.x-0.3-rc2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
site not found failures on delete tasks should not be fatal: if the site doesn't exist, just remove it, as much as you can, then maybe that will give a chance to an eventual verify task to pick up the pieces or something.
just failing to delete is annoying.
Comments
#1
This should also apply to Disable task.. if you know your site is broken / removed from the filesystem and you can't restore it (*cough* where are your backups) , you should be able to Disable, then Delete, the site.
#2
Actually, this bleeds into the Backup task that is initiated, see comment #4 in #529348: disable can still fail disabling damaged sites. I think this makes this ticket really a duplicate of that other (or vice versa, but the other has a patch, which is awaiting feedback from Adrian). If this isn't really a duplicate please reopen.
#3
< duplicate of #2, weird d.o issues at the time. >