Using hosting_quota, the quota appears to total number of site nodes, rather than the sites provisioned, for a client.

To replicate this bug, create a client with a quota, then create a site. Disable and then delete the site using the hosting interface (not via content management). On the client view, the quota will still show one site used, even though the client doesn't have any sites. Now, delete the site node, and the quota will calculate properly.

CommentFileSizeAuthor
#2 hosting-site-usage-query-898732-2.patch1.01 KBsfyn

Comments

sfyn’s picture

sfyn commented
Assigned: Unassigned » sfyn

This just requires an adjustment to the hosting_site quota implementation. I will hop right to it.

sfyn’s picture

sfyn commented
Status: Active » Needs review
StatusFileSize
new hosting-site-usage-query-898732-2.patch1.01 KB

Here's a patch for this issue. It counts disabled sites against the quota but not deleted sites.

sfyn’s picture

sfyn commented
Status: Needs review » Fixed

We just pushed this to HEAD on git.aegirproject.org. Yay!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit b178b88 on 6.x-2.x, 7.x-3.x, dev-ssl-ip-allocation-refactor, dev-sni, dev-helmo-3.x by sfyn: 
    Modify site usage query to fix #898732 on drupal.org

  • Commit b178b88 on 6.x-2.x, 7.x-3.x, dev-ssl-ip-allocation-refactor, dev-sni, dev-helmo-3.x by sfyn: 
    Modify site usage query to fix #898732 on drupal.org