Bug 1308697 - VMs stuck in "Waiting for Launch" state until engine restarted, yet VMs were actually running on the host.
Summary: VMs stuck in "Waiting for Launch" state until engine restarted, yet VMs were ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.7
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Vinzenz Feenstra [evilissimo]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-15 19:17 UTC by Gordon Watson
Modified: 2019-10-10 11:16 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-25 07:48:22 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gordon Watson 2016-02-15 19:17:53 UTC
Description of problem:

After some VMs were restarted on a specific host, they got stuck in a 'Waiting for Launch' state, but only as seen by the engine. On the host, they were all 'Up' and the guests were accessible and working as expected.

As a test, one of these VMs was started on a different host and it came up ok. When it was then started on the same host as the ones that were "stuck", it too became stuck in 'Waiting for Launch'.

This sounded like a host-related issue at first, but since the easiest thing to try was to restart ovirt-engine, that was performed and that resolved the problem. Nothing was done of that host at all to affect this.


Version-Release number of selected component (if applicable):

RHEV 3.5.7
RHEV-H 7.2 (20160105.1.el7) hosts 


How reproducible:

Not.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 12 Vinzenz Feenstra [evilissimo] 2016-02-24 08:27:49 UTC
Ok after all our investigations did go no where, I need to ask some more questions:

@Gordon:
- Are/Were there any 'Stateless' VMs running on the affected host?
- Is that issue still reproducible to the customer? If so, could you please try to give some more information on what you do when this happens?


Note You need to log in before you can comment on or make changes to this bug.