Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5241318A4E for ; Wed, 5 Aug 2015 13:44:11 +0000 (UTC) Received: (qmail 89807 invoked by uid 500); 5 Aug 2015 13:44:05 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 89771 invoked by uid 500); 5 Aug 2015 13:44:04 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 89761 invoked by uid 500); 5 Aug 2015 13:44:04 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 89758 invoked by uid 99); 5 Aug 2015 13:44:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2015 13:44:04 +0000 Date: Wed, 5 Aug 2015 13:44:04 +0000 (UTC) From: "Wido den Hollander (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CLOUDSTACK-8648) "Unable to get storage implementation" when copying template from NFS to S3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wido den Hollander resolved CLOUDSTACK-8648. -------------------------------------------- Resolution: Fixed Assignee: Wido den Hollander Merged into master > "Unable to get storage implementation" when copying template from NFS to S3 > --------------------------------------------------------------------------- > > Key: CLOUDSTACK-8648 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8648 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Secondary Storage > Affects Versions: Future, 4.5.2 > Reporter: Wido den Hollander > Assignee: Wido den Hollander > Labels: qcow2, s3, secondary_storage > Fix For: Future > > > In the SSVM this can be observed: > 2015-07-17 12:12:56,675 WARN [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-11:null) Failed to get virtual size, returning file size instead: > javax.naming.ConfigurationException: Unable to get storage implementation > at com.cloud.storage.template.QCOW2Processor.configure(QCOW2Processor.java:95) > at org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getVirtualSize(NfsSecondaryStorageResource.java:828) > at org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copyFromNfsToS3(NfsSecondaryStorageResource.java:886) > at org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copyFromNfsToImage(NfsSecondaryStorageResource.java:618) > at org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:645) > at org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:233) > at com.cloud.agent.Agent.processRequest(Agent.java:503) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) > at com.cloud.utils.nio.Task.run(Task.java:84) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > The problem is this: > processor.configure("template processor", new HashMap()); > return processor.getVirtualSize(file); > It confitures the processor with a empty HashMap, but the check in the processor is: > public boolean configure(String name, Map params) throws ConfigurationException { > _storage = (StorageLayer)params.get(StorageLayer.InstanceConfigKey); > if (_storage == null) { > throw new ConfigurationException("Unable to get storage implementation"); > } > Since the HashMap is empty null is returned and this exception is thrown. > No need to configure the Processor as far as I can see. -- This message was sent by Atlassian JIRA (v6.3.4#6332)