Quota modification backwards it seems.
Greetings,
When overselling is disabled for accounts, if a user has accounts which are currently over their allocated package limits, it seems that the user is 'stuck' here.
The user cannot lower quotas on existing accounts, because, quota
The user cannot create new accounts because, quota
This results in a lose/lose situation here, unfortunately.
Ideally, if the user is trying to lower quotas, limits should not be checked, only if they're trying to raise them.
-
The user cannot lower quotas on existing accounts, because, quota The user cannot create new accounts because, quota
Hello, I've been unable to reproduce an error message when reducing the quota on existing accounts under a reseller that's reached it's allocated package limits. Could you provide the full step-by-step instructions you are using to reproduce the issue, in addition to the specific privileges defined for the reseller? Thank you.0 -
The problem in this case is not as simple as just one account. I verified this over multiple machines, across multiple accounts over the past few days, and the end result is always the same. Reseller A requests downgrade of package. Their current package allows for overselling (different structure entirely), and they have some crazy allocations of quotas (not actual usage) on their packages. When downgraded to a package that does not allow for overselling, the overselling limits kick in. If the user tries to modify their accounts so that they are in check, they're told they can't. The catch to this here is that the user has multiple accounts with massive quotas (again, just quotas, not actual usage). So, modifying just one of these won't bring it under quota, which means that the user cannot actually edit the quota for the account, move on to the next, etc... The only solution to this is to temporarily allow overselling so that the user can get their quota usage back in check, and then disable this in the reseller package. Obviously, that's more work and causes more frustration from both the staff and customer perspective. Something's wrong with how you're looking at quota math. If new quota < old quota, then there really isn't any need for a check here, or there shouldn't be. 0 -
Hello, Thank you for providing additional information. Based on your response, here's a breakdown of the scenario you are describing: 1. Overselling is enabled on a reseller account, and thus the reseller account is limited by actual usage rather than the defined limit. 2. The reseller, because overselling is enabled, then creates several accounts or packages without a concern for the disk space or bandwidth limits that are defined. 3. Overselling is then disabled for the reseller, and thus attempts to lower the disk space or bandwidth limits fail because the lowered limit for a single account or package isn't enough to bring the overall values low enough to meet the resource limitations assigned to the reseller. Internal case CPANEL-3852 is open to address the lack of ability for a reseller to upgrade/downgrade existing packages once it's at it's resource limit. I've linked this thread to the case, and will update you with more information as it becomes available. You may also want to consider opening a feature request for changes to the core reseller functionality to address this concern: 0
Please sign in to leave a comment.
Comments
3 comments