Compute offering is not listed for vm when using disk offering strictness parameter

[lsgalves]

ISSUE TYPE

• Bug Report

COMPONENT NAME

API

CLOUDSTACK VERSION

4.19.1.2

CONFIGURATION

n/a

OS / ENVIRONMENT

n/a

SUMMARY

When scaling a VM created with a compute offer created with the disk offering strictness parameter, other offers are not listed (even though there are others in the same zone with the same access options and also with the disk offering strictness parameter):

According to the option description, it should not be allowed to change the disk offering for the ROOT disk after the VM is deployed:

I don't know if there could be a connection, but the current behavior is to not allow changing the disk provision even during VM deployment:

I believe this was not the expected behavior.

STEPS TO REPRODUCE

1. Create two compute offerings with the disk offering strictness parameter
2. Create a virtual machine with 1 first compute offer created
3. Change the offer to the second one created

EXPECTED RESULTS

That it is possible to change the disk offering only during the deployment of the VM even if an offering with the disk offering strictness option has been chosen. And that it lists and allows scaling the machine to other computing offerings that also have the disk offering strictness option.

ACTUAL RESULTS

Compute offers are not listed when trying to scale the instance.

[kiranchavala]

Able to reproduce the issue

The disk strictness related service offerings are not listed when scaling of a virtual machine is performed

[DaanHoogland]

@kiranchavala @lsgalves is this a UI only issue?

[matheusfontes]

@kiranchavala @lsgalves is this a UI only issue?

No.
It can be reproduced by api/cloudmonkey

[lsgalves]

Sorry, please ignore this issue. The problem was occurring because the "Compute only disk offering" option was also enabled, so in this case there is no other offering with the same disk offering and therefore nothing is listed.

However, when scaling the offering the problem was different. When scaling I receive the error: "Unable to Scale VM, since disk offering id associated with the old service offering is not same for new service offering":

I noticed that both offers point to the same diskofferingid, this error should not occur.