Bug 1164572
| Summary: | Start two engine VMs on two hosts not show any info messages and fail with -243 error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Artyom <alukiano> | ||||
| Component: | ovirt-hosted-engine-ha | Assignee: | Doron Fediuck <dfediuck> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.5.0 | CC: | dfediuck, ecohen, gklein, istein, lsurette, msivak, ylavi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.0.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | sla | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-09-02 09:58:40 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Martin, after recent changes in metadata file, what's the best way for getting the real status of the env after such error? Sandro: what changes? the real status is still reported, we just do not know how to detect that VM could not be started because of sanlock conflict (which is not a bug in some cases). We need some improved error code reporting from libvirt to do that probably.. or logfile parsing. *** This bug has been marked as a duplicate of bug 1150087 *** |
Created attachment 958020 [details] agent and vdsm logs Description of problem: Start two engine VMs on two hosts not show any info messages and fail with -243 error, because second host try to acquire sanlock to start vm, but fail, first host still hold lease. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.2.1-3.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Have hosted-engine environment with two hosts 2. Run vm on first host 3. Try to run vm also on second host(hosted-engine --vm-start) Actual results: Command show create vm(vdsClient format) and no any info message, also in vdsm log I see error -243 Expected results: Info message that vm already run on another host. Additional info: