cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8847) ListServiceOfferings is returning incompatible tagged offerings when called with VM id
Date Mon, 07 Dec 2015 09:11:10 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044614#comment-15044614
] 

ASF GitHub Bot commented on CLOUDSTACK-8847:
--------------------------------------------

Github user DaanHoogland commented on the pull request:

    https://github.com/apache/cloudstack/pull/823#issuecomment-162454833
  
    The code looks good but I am wondering about the functionality. The prior situation was
that the new offering should have a subset of the old one. Now it has to have a superset.
Why not an exact match? What are scenarios and what about users relying on the old behaviour?


> 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)

Mime
View raw message