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

Min Chen commented on CLOUDSTACK-1987:
--------------------------------------

Ryan's analysis is correct. There is also an issue exposed in our current 
implementation in QueryManagerImpl.searchForServiceOfferingInternal, where we 
are showing those public offering if name or keyword is specified, this is 
incorrect as well (similar to CLOUDSTACK-1989). I am fixing this by removing 
that OR clause (OR (service_offering_view.domain_id IS NULL AND 
service_offering_view.system_use = ? )) from searchForServiceOfferingInternal 
logic. This needs to be fixed for SearchForDiskOffering as well, which will 
have the same issue.
                
> Deleted service offerings owned by a domain show up to domain users
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1987
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1987
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>            Reporter: Marcus Sorensen
>            Assignee: Min Chen
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Create a domain
> create an account in that domain
> via the API, create a service offering and assign it to that domain
> delete the service offering
> log in as the domain user, attempt to create an instance, and see that the 
> deleted offering shows up
> log in as root admin, notice that the deleted offering does not show up
> This can cause instance deployment to fail when users select non-valid 
> offerings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to