[
https://issues.apache.org/jira/browse/CLOUDSTACK-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851910#comment-13851910
]
Harikrishna Patnala commented on CLOUDSTACK-4904:
-------------------------------------------------
the template_View schema is defined such that entries in the template_view are
only active templates.
CREATE VIEW `cloud`.`template_view` AS
select
vm_template.id,
vm_template.uuid,
vm_template.unique_name,
vm_template.name,
....
where
vm_template.state='Active';
In CS when we remove templates we mark them as inactive in DB. Then
template_view doesnot contains the removed entries, which means we cannot
retrieve removed entries by any search criteria.
Alex added that where clause on master/4.3
commit abbae2aa87471274cffa35b54ae8157c1efaade9 (4.3 commit)
Author: Alex Huang <alex.hu...@citrix.com>
Date: Mon Aug 26 17:30:58 2013 -0700
Fixed the problem with offerings and templates. These two items due to
a previous patch all the way back in 2.1.x versions uses the removed column
incorrectly. No one fixed since then. Hence, there's a bunch of
findbyidincludingremoved calls in the cloudstack code around these two items.
Some how my code worked when I submitted my patch. But later came across this
issue.
> Unable to see a derieved template if the parent template is deleted
> -------------------------------------------------------------------
>
> Key: CLOUDSTACK-4904
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4904
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template
> Affects Versions: 4.2.0
> Reporter: Harikrishna Patnala
> Assignee: Harikrishna Patnala
> Priority: Critical
> Fix For: 4.3.0
>
>
> Functionality required/broken - For a template, if the parent template info
> (template Id) is provided in the listTemplates API then one should be able to
> query for the parent template id as well (whether existing/removed doesn't
> matter)
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
