Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-5157

Virtualmin: Upgrading/Downgrading does not apply new plan resources

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.9.3
    • Fix Version/s: 5.10.0-b2
    • Component/s: Modules
    • Labels:
      None

      Description

      When upgrading/downgrading plans (plans are configured in Virtualmin to set resources, e.g. 5GB disk or 10GB disk, etc), Blesta makes the API call to change the plan, but not the call to apply the plan. So while the account reflects the new plan, it does not actually reflect the new plan's resource limits.

      The --apply-plan param should be provided instead of the plan param. See https://www.blesta.com/forums/index.php?/topic/25643-fix-for-bug-in-virtualmin-module-of-blesta-that-prevents-changed-plan-limits-being-applied/ for the report a suggested fix.

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Description When upgrading/downgrading plans (plans are configured in Virtualmin to set resources, e.g. 5GB disk or 10GB disk, etc), Blesta makes the API call to change the plan, but not the call to apply the plan. So while the account reflects the new plan, it does not actually reflect the new plan's resource limits.

        The --apply-plan param should be provided instead of the plan param. See https://www.blesta.com/forums/index.php?/topic/25643-fix-for-bug-in-virtualmin-module-of-blesta-that-prevents-changed-plan-limits-being-applied/ for the report and suggested fix.


        When upgrading/downgrading plans (plans are configured in Virtualmin to set resources, e.g. 5GB disk or 10GB disk, etc), Blesta makes the API call to change the plan, but not the call to apply the plan. So while the account reflects the new plan, it does not actually reflect the new plan's resource limits.

        The --apply-plan param should be provided instead of the plan param. See https://www.blesta.com/forums/index.php?/topic/25643-fix-for-bug-in-virtualmin-module-of-blesta-that-prevents-changed-plan-limits-being-applied/ for the report a suggested fix.


        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.10.0-b2 Sprint 1 [ 199 ]
        abdy Abdy Franco made changes -
        Assignee Abdy Franco [ abdy ]
        abdy Abdy Franco made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        abdy Abdy Franco made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 6 minutes [ 360 ]
        Worklog Id 16955 [ 16955 ]
        abdy Abdy Franco made changes -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        jonathan Jonathan Reissmueller made changes -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              14/May/24

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 6 minutes
              6m

                Agile