Bug 1305809
| Summary: | [Cinder] - Running a stateless VM leaves a locked snapshot and the VM cannot be started | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Maor <mlipchuk> |
| Component: | BLL.Storage | Assignee: | Maor <mlipchuk> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Natalie Gavrielov <ngavrilo> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.3.1 | CC: | amureini, bugs, tnisan, ylavi |
| Target Milestone: | ovirt-3.6.3 | Flags: | tnisan:
ovirt-3.6.z?
ylavi: exception? rule-engine: planning_ack+ tnisan: devel_ack+ rule-engine: testing_ack? |
| Target Release: | 3.6.3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-23 13:31:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1270725, 1288157 | ||
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. |
Description of problem: Following the fix of create snapshot with Cinder disks for failure flow, The child command callback does not call the parent any more, but it is all being done through ConcurrentChildCommandsExecutionCallback. For stateless VM, part of the logic is to create a stateless snapshot which being called from RunVmCommand. before introducing ConcurrentChildCommandsExecutionCallback the end action was called from CreateCinderSnapshotCommand endCommand though now running a stateless VM creates a stateless snapshot and leaves the snapshot in lock status. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Run a stateless VM with Cinder disk 2. 3. Actual results: The stateless snapshot is in lock status for ever. Expected results: The stateless snapshot should be created and the stateless VM should run Additional info: