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 C372C1020F for ; Thu, 27 Nov 2014 10:45:13 +0000 (UTC) Received: (qmail 78646 invoked by uid 500); 27 Nov 2014 10:45:13 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 78601 invoked by uid 500); 27 Nov 2014 10:45:12 -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 78588 invoked by uid 500); 27 Nov 2014 10:45:12 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 78580 invoked by uid 99); 27 Nov 2014 10:45:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Nov 2014 10:45:12 +0000 Date: Thu, 27 Nov 2014 10:45:12 +0000 (UTC) From: "Hiroki Ohashi (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-7412) Can't create proper template from VM on S3 secondary storage environment 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-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227503#comment-14227503 ] Hiroki Ohashi commented on CLOUDSTACK-7412: ------------------------------------------- Patch url is below. https://reviews.apache.org/r/28511/ > Can't create proper template from VM on S3 secondary storage environment > ------------------------------------------------------------------------ > > Key: CLOUDSTACK-7412 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7412 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Storage Controller, Template > Affects Versions: Future, 4.2.1, 4.3.0, 4.4.0, 4.5.0 > Environment: CloudStack 4.3.0 on CentOS 6.5. > KVM Hypervisor. > using S3 provider as socondary storage. The storage system is using RADOS. > using local storage as primary storage. > Reporter: Akihiko Ota > Fix For: Future, 4.5.0, 4.6.0, 4.4.3, 4.3.2 > > > When I create more than one templates from an existing virtual machine, the second and the subsequent template is created the same as first one. > It doesn't occur in the case of using NFS secondary storage. So I guess this is the S3 provider specific issue. > This could reproduce as following procedure. > (1) create a virtual machine (name "foo" tentatively), and modify some files on ROOT volume of "foo". > (2) stop "foo". and create template "template-foo.1" from ROOT volume of "foo". > (3) reboot (not re-create) "foo", and modify some files on ROOT volume again. > (4) stop "foo". and create template "template-foo.2" from ROOT volume of "foo". > I expect that template-foo.2 keeps (3)'s changes. But template-foo.2 is the same as template-foo.1. (3)'s changes are not recorded. > As of (4), CloudStack outputs the following DEBUG message to cloudstack-management.log. > 2014-08-07 19:23:20,094 DEBUG [o.a.c.s.c.m.StorageCacheManagerImpl] (Job-Executor-58:ctx-b00fbe22 ctx-6339bae6) there is already one in the cache store > When creating templates on NFS secondary storage environment, this message is not output. > This issue also exists on CloudStack 4.2.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)