Closed (fixed)
Project:
Hosting
Version:
5.x-0.2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Nov 2008 at 04:51 UTC
Updated:
17 Apr 2009 at 15:40 UTC
Currently when a site fails the status is 'site not installed, site enabled'. The fact that the site is enabled but not installed stops the user from running other tasks like disable site. The status of a failed site install should be 'site not installed, site disabled'.
Comments
Comment #1
anarcat commentedSo the issue here is that the flags are set in the post_install() hook. That hook is (rightly) run only when the site is successfully ran.
My guess is that we could use a rollback hook, similar to what the provision module is doing, to handle those situations.
Comment #2
anarcat commentedActually, thinking aloud here: maybe the site should be marked as disabled as long as it's not installed. The install task currently sets the enable flag on the site, so that wouldn't be a problem....
Comment #3
adrian commentedI think sites should start off as disabled till installed. This would solve this issue.
Comment #4
anarcat commentedWe just have to fix node_site_insert somewhere...
Comment #5
adrian commentedThe problem is we can't initialize them to any of the 'anti' statuses. or weird things happens.
Comment #6
anarcat commentedSo we talked about this quickly and I feel that yes, HOSTING_STATUS_DISABLED should be an explicitely set value.
Comment #7
anarcat commentedAlso, 'verify' tasks that lead to 'site not installed yet' should mark the site as 'not installed' so it can be installed again or removed...
Comment #8
anarcat commentedI think we should target this for 0.2..
Comment #9
anarcat commentedJust a quick note to mention that some work has been done in this direction in the provision module to refactor the error handling and codes, so this should be easier now.
Comment #10
adrian commentedFixed in #333952