| Summary: | Remove snapshot failed because vm was running and guest agent does not respond | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lev Veyde <lveyde> |
| Component: | ovirt-engine | Assignee: | Nobody <nobody> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.3.0 | CC: | abaron, acathrow, bazulay, eedri, gickowic, gklein, hateya, iheim, knesenko, lpeer, lveyde, mbourvin, michal.skrivanek, nsoffer, ofrenkel, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | Keywords: | AutomationBlocker, AutomationTriaged |
| Target Release: | 3.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-19 07:39:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Comment 2
Nir Soffer
2013-12-11 10:11:33 UTC
This has nothing to do with vdsm: Cannot remove Snapshot. At least one of the VMs is not down Is the VM still running? if so, my guess would be this is a bug in the test Was this test or test running before it modified since build is25? which guest agent? (In reply to Michal Skrivanek from comment #6) > which guest agent? Thats what the log say: Thread-4825::DEBUG::2013-12-10 14:29:01,038::libvirtconnection::108::libvirtconnection::(wrapper) Unknown libvirterror: ecode: 86 edom: 10 level: 2 message: Guest agent is not responding: Guest agent not available for now Thread-4825::DEBUG::2013-12-10 14:29:01,039::vm::3855::vm.Vm::(snapshot) vmId=`427f9ffb-91fd-46c5-83c6-d504bc3dfca5`::Snapshot failed using the quiesce flag, trying again without it (Guest agent is not responding: Guest agent not available for now) Ok. So was it a Win guest and Qemu-ga was installed? (If so please move to integration to resolve) Other cases are NOTABUG as we don't manage qemu-ga The rest is a storage issue which I understood works as designed, i.e. The environment was too busy and test should report it as such (please move/open a followip for fixing tests) (In reply to Michal Skrivanek from comment #8) > Ok. So was it a Win guest and Qemu-ga was installed? (If so please move to > integration to resolve) > Other cases are NOTABUG as we don't manage qemu-ga > > The rest is a storage issue which I understood works as designed, i.e. The > environment was too busy and test should report it as such (please move/open > a followip for fixing tests) I think the test runs against Linux guest. Gadi, Meital what agents are required for this test to run ? Linux (In reply to Meital Bourvine from comment #11) > Linux What I meant is what agents inside the Linux guest are required - is it only RHEV-Agent or i.e. Qemu-Guest-Agent is also required for this test to succeed ? supposedly not a blocker then, as this is most likely NOTABUG (In reply to Michal Skrivanek from comment #16) > supposedly not a blocker then, as this is most likely NOTABUG Job looks ok now. There was an infra issue QE fixed it. |