[
https://issues.apache.org/jira/browse/CLOUDSTACK-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048610#comment-15048610
]
ASF GitHub Bot commented on CLOUDSTACK-8847:
--------------------------------------------
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/823#issuecomment-163212979
@nitin-maharana : Then you are saying it must be an exact match. Now a
compute offering that had (x,y) can be replaced with one that has (x,y,z) while
the VM deployed with it is running on a host that only supports (x,y). Will it
be automagically be migrated, or only on a reboot. or will it fail to reboot
because of the tags. I still am weary about the functional spec this implies.
> ListServiceOfferings is returning incompatible tagged offerings when called
> with VM id
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8847
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8847
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Nitin Kumar Maharana
>
> When calling listServiceOfferings with VM id as parameter. It is returning
> incompatible tagged offerings. It should only list all compatible tagged
> offerings. The new service offering should contain all the tags of the
> existing service offering. If that is the case It should list in the result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
