H Qian, Submit a bug report in jira [1]. If you have a fix for the 'master' branch submit a review request in the review board [2] be sure to add enough contents to the fields and set the group to 'cloudstack'. Find the people most involved with the code you changed and ask them to review. If you feel it is really a bug and must be ported to 4.3 add a second review request with changes to the branch '4.3-forward'. then ask the release manager to apply it to the 4.3 branch.
[1] https://issues.apache.org/jira/browse/CLOUDSTACK [2] https://reviews.apache.org/ On Tue, Mar 4, 2014 at 3:40 AM, Qian Shaohua <qianshao...@ctsi.com.cn> wrote: > Hi, > > We meet the follow case in 4.2.1: > > 1. deploy a vm > > 2. stop it > > 3. restore it, ROOT volume is allocated. > > 4. create vm snapshot > > Step 4 should always fail, but a createVMSnapshot job is still created > without checking volume state. > > The problem seems also in 4.3 according to the source > VMSnapshotManagerImpl.allocVMSnapshot(). > > I'm not a committer but eager to be. How to do with it? > > > > > > --Qian > -- Daan
