[
https://issues.apache.org/jira/browse/CLOUDSTACK-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050444#comment-15050444
]
ASF GitHub Bot commented on CLOUDSTACK-8847:
--------------------------------------------
Github user nitin-maharana commented on the pull request:
https://github.com/apache/cloudstack/pull/823#issuecomment-163550095
@DaanHoogland : No, it needn't not be an exact match but the new one should
be a superset of the current one. According to your scenario, as the new one
supports (x,y) as well as supports an extra tag (z). The interpretation will be
more clear if we think of this in terms of venn diagram.
The migration will fail in running mode. Dynamic scaling cannot be done. It
will only be done on reboot.
> 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)
