Posted by Anonymous on September 15, 2009 at 12:18am
I found a way to break Aegir.
Create a site such as example.com.
Disable example.com.
Go to admin/content/node and delete example.com site while it's still disabled.
Create a new example.com site.
When you try to go to the new example.com site, you will be redirected to an Aegir page telling you that example.com is disabled, even though the old example.com has been deleted and the new example.com is enabled.
I hope that explanation is clear enough.
Thanks,
Doug Gough
Comments
Hi! So this is because the
Hi!
So this is because the Disable task adds a rewrite rule in the apache config to rewrite to a 'disabled' page in aegir. Because you haven't properly deleted the site via the Delete task, the apache vhost config for the old site still exists.
But we should not allow the new site to be created with the same name if the old one hasn't been properly deleted yet.
Thanks for this information: please submit it as a ticket in the issue queue.
Thanks for your help. I've
Thanks for your help. I've submitted a ticket.