Bug 867335
| Summary: | engine: there is no event sent to event log for cancel migration | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dafna Ron <dron> | ||||||
| Component: | ovirt-engine | Assignee: | Arik <ahadas> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Pavel Stehlik <pstehlik> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 3.1.0 | CC: | dyasny, hateya, iheim, lpeer, michal.skrivanek, oramraz, Rhev-m-bugs, yeylon, ykaul | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | virt | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-11-19 12:01:46 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: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 628665 [details]
logs
There is no such event for synchronous actions by design, as the results for those actions should appear quickly. If there is a scenario in which it takes a long time to get the result for such action, it should be declared as a different bug |
Created attachment 628664 [details] screen shot Description of problem: when we press cancel migration on a vm, there is no even shown in the event log. only end action status is shown in event log. this means that the user has no idea what is the status of the action until we get a return for command. Version-Release number of selected component (if applicable): si20 How reproducible: 100% Steps to Reproduce: 1. in a two hosts cluster with NFS storage migrate a vm 2. cancel the migration 3. please note that if we block connectivity to storage from source vds we can see it more clearly since we see nothing for a long time and than get the error on the failure of cancel migration. Actual results: we get the end result of the migration but not the event on starting the migration Expected results: we should get even for start of action and end of action. Additional info: screen shot attached. here you can see that only the "success" of the cancel migration is reported: 2012-Oct-17, 12:07:09 Starting migration of VM RHEL-NFS-2 from Host gold-vdsc to Host gold-vdsd (User: admin@internal.). 2012-Oct-17, 12:07:08 Migration failed due to Error: Fatal error during migration (VM: RHEL-NFS-2, Source Host: gold-vdsc). Trying to migrate to another Host. 2012-Oct-17, 12:07:07 Migration cancelled for VM: RHEL-NFS-2 when my source vds was blocked to storage I could only see the failed cancel: 2012-Oct-17, 12:01:06 Failed to cancel migration for VM: RHEL-NFS-9