We also encountered this issue when we ran test on object_store branch before sending merge request, then we realize that this has been broken in master and consider to fix that after merging object_store branch to master. But from looking through comments in https://issues.apache.org/jira/browse/CLOUDSTACK-1353 you attached here, now I am feeling that recurring snapshot is even broken in 4.1.0 branch (see Deepti's comment in the bug). If that is the case, this may need to be considered as blocker for 4.1.
Thanks -min On 5/23/13 12:56 AM, "Nguyen Anh Tu" <ng.t...@gmail.com> wrote: >Hi fork, > >I'm using CS 4.2.0-snapshot + Xen XCP. I set a recurring snapshot and get >this error: > >2013-05-23 09:30:40,150 DEBUG [storage.snapshot.SnapshotSchedulerImpl] >(SnapshotPollTask:null) Scheduling 1 snapshot for volume 7 for schedule >id: >2 at 2013-05-23 02:27:00 GMT >2013-05-23 09:30:40,190 WARN [storage.snapshot.SnapshotSchedulerImpl] >(SnapshotPollTask:null) Scheduling snapshot failed due to >java.lang.NullPointerException >2013-05-23 09:30:40,191 WARN [utils.db.Merovingian2] >(SnapshotPollTask:null) Was unable to find lock for the key >snapshot_schedule2 and thread id 21407801 > > >I found two same issues on jira. How can we fix it or I miss some new >code? > >https://issues.apache.org/jira/browse/CLOUDSTACK-2523 >https://issues.apache.org/jira/browse/CLOUDSTACK-1353 > > >-- > >N.g.U.y.e.N.A.n.H.t.U