Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 23 Dec 2014 04:23:13 +0000 (UTC)
From: "Likitha Shetty (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12763376.1419308573000.89122.1419308593633@Atlassian.JIRA>
In-Reply-To: <JIRA.12763376.1419308573000@Atlassian.JIRA>
References: <JIRA.12763376.1419308573000@Atlassian.JIRA>
 <JIRA.12763376.1419308573981@arcas>
Subject: [jira] [Created] (CLOUDSTACK-8107) Failed to create snapshot from
 volume when the task is performed repeatedly in zone wide primary Storage.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Likitha Shetty created CLOUDSTACK-8107:
------------------------------------------

             Summary: Failed to create snapshot from volume when the task is performed repeatedly in zone wide primary Storage.
                 Key: CLOUDSTACK-8107
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8107
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.5.0
            Reporter: Likitha Shetty
            Assignee: Likitha Shetty
            Priority: Critical
             Fix For: Future


+Steps to reproduce+
1. Setup a CS zone with a VMware DC.
2. Ensure the DC has 2 clusters with a host each.
3. Add 2 Cluster-Wide primary storage pool to each of the clusters.
4. Add a Zone-wide primary storage pool.
5. Deploy a VM with a data-disk. Ensure both the ROOT and Data disk of the VM is in the zone-wide storage pool.
6. Take snapshots for the Data volume till the operation fails.
In vCenter, the failure will be while Reconfiguring (worker)VM and the error will be '<>.vmdk was not found'.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)