cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanteswararao Talluri (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-2768) [SXM] snapshot on a migrated volume is getting NULL path
Date Thu, 30 May 2013 12:32:19 GMT
Srikanteswararao Talluri created CLOUDSTACK-2768:

             Summary: [SXM] snapshot on a migrated volume is getting NULL path 
                 Key: CLOUDSTACK-2768
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Snapshot
    Affects Versions: 4.2.0
            Reporter: Srikanteswararao Talluri
            Priority: Critical
             Fix For: 4.2.0

Steps to reproduce:
1. create two clusters [C1,C2]with two primary storages[P1,P2] respectively.
2. deploy a VM VM1 and attach 2 data volumes V1,V2.
3. migrate volume V1.
4.  While volume V1 is being migrated, Migrate VM1 with volumes to Cluster C2.

Step 4 will result in failure and all the volumes and VM should be as it was before migrate

5. Now, take a snapshot of volume V1 OR V2. This is updating the path in the snapshot table
as NULL, which in turn results in Null pointer exception on snapshot operations(template/volume
creation from snapshot)

              id: 3
  data_center_id: 1
      account_id: 2
       domain_id: 1
       volume_id: 25
disk_offering_id: 5
          status: BackedUp
            path: NULL
            name: sharedshared_tt_20130530164422
            uuid: 3ba59708-cb37-4019-a54c-5f6db4eaa36d
   snapshot_type: 0
type_description: MANUAL
            size: 107374182400
         created: 2013-05-30 16:44:22
         removed: NULL
  backup_snap_id: NULL
        swift_id: NULL
      sechost_id: NULL
    prev_snap_id: 0
 hypervisor_type: XenServer
         version: 2.2
           s3_id: NULL

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message