Bug 1163073
| Summary: | VM fail to launch or get stuck on launching state (VDSM does not recieve VM start due to timeout on VM start request). | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Nisim Simsolo <nsimsolo> | ||||||||||||||
| Component: | ovirt-engine | Assignee: | Nobody <nobody> | ||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||||||||||
| Severity: | urgent | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 3.5.0 | CC: | ecohen, gklein, iheim, lpeer, lsurette, nsimsolo, ofrenkel, oourfali, pkliczew, rbalakri, Rhev-m-bugs, yeylon | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | 3.5.0 | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | virt | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2014-11-17 13:17:13 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: |
|
||||||||||||||||
|
Description
Nisim Simsolo
2014-11-12 10:39:29 UTC
Created attachment 956712 [details]
engine log
engine log
Created attachment 956713 [details]
vdsm.log
Created attachment 956714 [details]
libvirtd.log
Created attachment 956715 [details]
sanlock.log
looks like a temp network error, in the log it seems this happened only once.. does this happen all the time? does this happen to all vms or just one? also, vdsm log does not correspond to the engine log, the failure is around 2014-11-12 09:28:53,037 (engine log) but vdsm log only starts 2 hours later at Dummy-70::DEBUG::2014-11-12 11:01:02,785.. please attach the vdsm.log for the same time of the error. Created attachment 956758 [details]
earlier vdsm log
still not the right one... we need the log that contains the time of the error, which is 2014-11-12 09:28:53 anyway might be duplicate of Bug 1143968 Created attachment 957086 [details]
vdsm.log.13.xz
thanks, i dont see anything on vdsm.log during this time, also if the vm doesnt start on vdsm at all, i'm not sure this fit the scenario of Bug 1143968 not sure what can cause this: 2014-11-12 09:31:53,536 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) Connecting to /10.35.4.65 if this doesn't happen consistently, not sure how interesting it is. on the other hand, i don't see any other comunication errors with this host during this time.. Oved, can someone take a look? it looks more around engine-vdsm communication (In reply to Omer Frenkel from comment #9) > thanks, i dont see anything on vdsm.log during this time, also if the vm > doesnt start on vdsm at all, i'm not sure this fit the scenario of Bug > 1143968 > > not sure what can cause this: > 2014-11-12 09:31:53,536 INFO > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) > Connecting to /10.35.4.65 > Doesn't seem problematic, but perhaps Piotr can take a look. Piotr? This bug is duplicate of 1148583 *** This bug has been marked as a duplicate of bug 1148583 *** |