----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5806/#review9018 -----------------------------------------------------------
server/src/com/cloud/storage/snapshot/SnapshotManagerImpl.java <https://reviews.apache.org/r/5806/#comment19172> Why this new if (!backedUp) block when you already have this block above ? Please put the decrementing logic in above block server/src/com/cloud/storage/snapshot/SnapshotManagerImpl.java <https://reviews.apache.org/r/5806/#comment19173> Did you inquire how we solve this problem in other places in CS ? I cant approve this change since we dont want to reinvent the wheel if this has already been solved. If it hasn't been solved then I would want to raise this in the mailing list and hear out a good way of doing this. - Nitin Mehta On July 10, 2012, 1:32 p.m., deepti dohare wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/5806/ > ----------------------------------------------------------- > > (Updated July 10, 2012, 1:32 p.m.) > > > Review request for cloudstack. > > > Description > ------- > > Change: > 1. Before creating the snapshot, we synchronized checkResourcelimit to allow > the users to create the snapshot and increment the resource count. > 2. Depending on the failure of snapshot creation/ backup, we are decrementing > the resource count. > > > This addresses bug CS-15430. > > > Diffs > ----- > > server/src/com/cloud/storage/snapshot/SnapshotManagerImpl.java 50dcf38 > > Diff: https://reviews.apache.org/r/5806/diff/ > > > Testing > ------- > > Steps to verify: > 1.Login as admin, set snapshot limit '3' for a user account > 2.login as user, create a VM1 with data volume > 3.trigger 3 create snapshot command from the above data volume, succeeded > 4.create one more snapshot, failed, "maximum limit exceeded for account user" > > > Thanks, > > deepti dohare > >
