You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/12/13 02:52:07 UTC

[jira] [Created] (CLOUDSTACK-5482) Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in "CreatedOnPrimary" state.

Sangeetha Hariharan created CLOUDSTACK-5482:
-----------------------------------------------

             Summary: Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind  snaphots in "CreatedOnPrimary" state.
                 Key: CLOUDSTACK-5482
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5482
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.3.0
         Environment: Build from 4.3
            Reporter: Sangeetha Hariharan
             Fix For: 4.3.0


Set up :
Advanced Zone with 2 5.1 ESXI hosts.

Steps to reproduce the problem:

1. Deploy 5 Vms in each of the hosts , so we start with 11 Vms.
2. Start concurrent snapshots for ROOT volumes of all the Vms.
3. Shutdown the Secondary storage server when the snapshots are in the progress.
4. Bring the Secondary storage server up after 1 hour.

When the secondary storage was down , 2 of the  snapshots were already completed. 5 of them were in progress and the other 4 had not started yet.

Once the secondary store was brought up , I see the snapshots that were in progress actually continue to download to secondary and succeed. But the other 4 snapshots error out. 

mysql> select volume_id,status,created from snapshots;
+-----------+------------------+---------------------+
| volume_id | status           | created             |
+-----------+------------------+---------------------+
|        22 | BackedUp         | 2013-12-12 23:24:13 |
|        21 | Destroyed        | 2013-12-12 23:24:13 |
|        20 | BackedUp         | 2013-12-12 23:24:14 |
|        19 | Destroyed        | 2013-12-12 23:24:14 |
|        18 | BackedUp         | 2013-12-12 23:24:14 |
|        17 | BackedUp         | 2013-12-12 23:24:14 |
|        16 | BackedUp         | 2013-12-12 23:24:14 |
|        14 | BackedUp         | 2013-12-12 23:24:15 |
|        25 | BackedUp         | 2013-12-12 23:24:15 |
|        24 | BackedUp         | 2013-12-12 23:24:15 |
|        23 | BackedUp         | 2013-12-12 23:24:15 |
|        22 | CreatedOnPrimary | 2013-12-12 23:53:38 |
|        21 | BackedUp         | 2013-12-12 23:53:38 |
|        20 | BackedUp         | 2013-12-12 23:53:38 |
|        19 | BackedUp         | 2013-12-12 23:53:39 |
|        18 | CreatedOnPrimary | 2013-12-12 23:53:39 |
|        17 | CreatedOnPrimary | 2013-12-12 23:53:40 |
|        16 | CreatedOnPrimary | 2013-12-12 23:53:40 |
|        14 | BackedUp         | 2013-12-12 23:53:40 |
|        25 | BackedUp         | 2013-12-12 23:53:41 |
|        24 | BackedUp         | 2013-12-12 23:53:41 |
|        23 | BackedUp         | 2013-12-12 23:53:42 |
|        21 | BackedUp         | 2013-12-13 00:53:37 |
|        19 | BackedUp         | 2013-12-13 00:53:38 |
+-----------+------------------+---------------------+
24 rows in set (0.00 sec)






--
This message was sent by Atlassian JIRA
(v6.1.4#6159)