Bug 1298223
| Summary: | removing automatic VM pool with running vms fails constantly | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Barak Korren <bkorren> |
| Component: | BLL.Virt | Assignee: | Shahar Havivi <shavivi> |
| Status: | CLOSED WORKSFORME | QA Contact: | meital avital <mavital> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.6.1.3 | CC: | bkorren, bugs, gklein, masayag, mgoldboi, tjelinek |
| Target Milestone: | ovirt-4.2.0 | Flags: | tjelinek:
ovirt-4.2?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-03 10:43:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
logs? I don't have the test system any more, so cannot provide logs at this time. Please follow steps to reproduce. does not seem as something dangerous, only an annoyance - targeting 4.0 for consideration. deferred to next version due to capacity. (In reply to Tomas Jelinek from comment #3) > does not seem as something dangerous, only an annoyance - targeting 4.0 for > consideration. And now? fix or defer? defer. Cannot reproduce, Try with 2-5 VMs with and without disks. Barak can you reproduce it? If you can reproduce it with engine logs please reopen the bug. Removing needinfo |
Description of problem: When removing an automatic pool with running VMs, the command will fail for the 1st time and succeed for the 2nd. Version-Release number of selected component (if applicable): oVirt Engine Version: 3.6.1.3-1.el7.centos How reproducible: Always Steps to Reproduce: 1. Create a VM pool from a template with a disk, set the pool size to at least 2 and set it to per-start at least 2 vms 2. wait for the vms to start up 3. try to remove the pool -> the VMs will be shut down but the removal task will fail and the pool will remain 4. try to remove the pool again -> this time the VMs and pool will be erased Actual results: Pool removal task fails Expected results: Pool removal task should succeed the first time