Solusvm Upgrade Not Changing Disk Space Allocation

[Rob T]

Blesta Version: 3.6.1

SolusVM Module Version:  3.4.2

SolusVM Version: 1.18.01 (latest)
 

Problem:  When processing an automated upgrade, Blesta is changing the RAM, bandwidth, and CPU core attributes for the new plan, but is not properly updating the HDD space attribute.  This is affecting VM's with KVM virtualization.  Unknown if other types are affected.

 

SolusVM API Log Output:

status => successnvserverid => 112nmsg => Virtual server plan changed (appears to be successful)

 

Steps to Recreate:

 

1 - Create new KVM VPS using Blesta via API

2 - Process upgrade order to higher package with more disk space than original plan

 

In our particular case, our basic plan includes 1GB RAM, 1TB bandwidth, 1CPU core, and 15GB HDD Space.  We noticed that several users who were attempting to process an upgrade order would get partically upgraded to our next plan properly (2GB RAM, 2TB bandwidth, 2 CPU Cores), but that the disk space reported in SolusVM would remain at 15GB.  Screen shot attached is the resulting resource information for an upgraded VM.

[Tyson]

Did you reboot the VM? I believe a disk space change requires reboot. If that doesn't resolve it, could you provide the module logs (under [Tools], click on the table row that corresponds to the SolusVM action) for that upgrade? There would likely be an entry for changing the hard disk space (i.e. "changeHdd") in the list.