sbrueseke commented on issue #7389:
URL: https://github.com/apache/cloudstack/issues/7389#issuecomment-1495450796

   I think I found the root cause of this. It is not an UI related issue, it is 
an api related one.
   When using command listServiceOfferings and parameter virtualmachineid and 
you provide an id of a VM using a custom offering with 
diskofferingstrictness=true, the api will not include this offering in the 
response and so the UI is not able to provide this offering.
   My humble opinion is that this is not correct behavior and you should be 
able to scale cpu and ram even if the used offer in uses strictness for the 
disk. Since scaleVirtualMachine is able to this using the same offering, 
listServiceOfferings should also include the used custom offering in the 
response.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to