You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No compute offerings listed when scaling a VM #12361
@itobin Unfortunately, I don't have version 4.22 available at the moment to try and reproduce the issue, but I can confirm that everything is working correctly in 4.20.2. This behavior is usually related to UI filtering rules. Just in case, please ensure that the current VM offering is compatible with the others. For instance, there might be restrictions based on access rights, project, domain, or storage type (e.g., shared vs. local in offering). Also, if the VM is powered on, make sure that all offerings were created with the 'dynamic scaling enabled' option.
@SviridoffA I think your right, it appears it something to do with the setting of the disk is shared on the plan.
When the VM was created, the option to create a disk on a seperate disk offering was used which was local. So this is potentially an issue as we just want to change the compute offering, not disk but appears this isnt possible unless we create more compute offerings that use local disk.
It could end up getting messy with lots of compute offerings.
Activity
SviridoffA commentedon Jan 1, 2026
@itobin Do you use any tags in your compute offerings? If so, please take a look at this issue #11407 and linked discussion.
itobin commentedon Jan 1, 2026
@SviridoffA no its fairly basic on all compute offerings
SviridoffA commentedon Jan 1, 2026
@itobin Unfortunately, I don't have version 4.22 available at the moment to try and reproduce the issue, but I can confirm that everything is working correctly in 4.20.2. This behavior is usually related to UI filtering rules. Just in case, please ensure that the current VM offering is compatible with the others. For instance, there might be restrictions based on access rights, project, domain, or storage type (e.g., shared vs. local in offering). Also, if the VM is powered on, make sure that all offerings were created with the 'dynamic scaling enabled' option.
itobin commentedon Jan 1, 2026
@SviridoffA I think your right, it appears it something to do with the setting of the disk is shared on the plan.
When the VM was created, the option to create a disk on a seperate disk offering was used which was local. So this is potentially an issue as we just want to change the compute offering, not disk but appears this isnt possible unless we create more compute offerings that use local disk.
It could end up getting messy with lots of compute offerings.
itobin commentedon Jan 1, 2026
worked around it, changed the disk offering to a shared disk. Let is copy over. Then the compute offerings showed up.
scaled up then changed the disk offering back so i think this is sorted now, thanks for the help