[
https://issues.apache.org/jira/browse/CLOUDSTACK-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799636#comment-13799636
]
Nitin Mehta commented on CLOUDSTACK-4896:
-----------------------------------------
Its not just the admin but the end user gets affected as well with no feedback
to them on the UI.
He/She with the current behaviour would just start seeing their templates
disappearing in case of any error on ssvm, only to dig into the logs for the
real issue.
Template Sync was a good mechanism to retry download for all the erred out
templates once the problem on ssvm is corrected.
I don’t think we are failing fast here. We used to fail similarly earlier, but
there was a retry mechanism in template sync and better feedb
I see that for uploaded volumes the experience is all the more bad. When
someone uploads a volume, if there is an error the volume persists on the UI
with no indication of error or anything(because volume_store_ref entry is
removed).
Instead it shows up as a normal data disk (as if added through "Add Volume")
and gets attached to the vm.
> Template store ref and template Sync
> -------------------------------------
>
> Key: CLOUDSTACK-4896
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4896
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Nitin Mehta
>
> I observed that while registering a template if we face an error we delete
> the entry from template store ref and hence template is not visible in the
> UI.
> This didn't use to happen pre 4.2 and we used to show the template in UI.
> Also we don't retry the errored out templates as part of template sync, this
> again is breaking the old behavior. I guess we should fix this right ?
> Thoughts/Comments ?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
