[
https://issues.apache.org/jira/browse/CLOUDSTACK-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993561#comment-13993561
]
Koushik Das commented on CLOUDSTACK-6623:
-----------------------------------------
The root cause for this is that both Simulator and XenServer secondary/image
store use NFS as provider and the driver map present in
ImageStoreProviderManagerImpl.java looks like below in a mixed setup having
both XS and simulator zones
{S3=org.apache.cloudstack.storage.datastore.driver.S3ImageStoreDriverImpl@40e2b1c0,
NFS=org.apache.cloudstack.storage.datastore.driver.SimulatorImageStoreDriverImpl@6303d587,
Swift=org.apache.cloudstack.storage.datastore.driver.SwiftImageStoreDriverImpl@10b7c4da}
So in case of XS, it goes to the SimulatorImageStoreDriverImpl and so register
template, template sync all are failing in the XS zone.
One way to fix this problem is to have a list of drivers for each provider type
and then select from that appropriately.
> register template dose not work as expected, when deploying simulator and xen
> zones simultaneously on a single management server.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6623
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6623
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Affects Versions: 4.4.0
> Reporter: Bharat Kumar
> Fix For: 4.4.0
>
>
> when we setup simulator and xenserver both in separate zones on a single
> management server, The register template always behaves as if it is executing
> on the simulator. i.e. register template is always successful and it dose not
> initiate the actual download when calling the register template API against
> xen-zone.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
