Bug 1019468 - ha agent don't handle vm status 'Waiting for Launch'.
Summary: ha agent don't handle vm status 'Waiting for Launch'.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-ha
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Greg Padgett
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-15 19:30 UTC by Leonid Natapov
Modified: 2016-06-12 23:16 UTC (History)
9 users (show)

Fixed In Version: ovirt-hosted-engine-ha-0.1.0-0.4.beta1.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 16:51:02 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0080 0 normal SHIPPED_LIVE new package: ovirt-hosted-engine-ha 2014-01-21 21:00:07 UTC
oVirt gerrit 20210 0 None None None Never

Description Leonid Natapov 2013-10-15 19:30:01 UTC
ha agent don't handle vm status 'Waiting for Launch',so if we read the status, the agent will think the vm is 'down'. it will cause to agent to try and start VM over and over again.

11:23:16,511::BindingXMLRPC::984::vds::(wrapper) client [127.0.0.1]::call vmCreate with ({'emulatedMachine':
11:23:27,233::BindingXMLRPC::984::vds::(wrapper) client [10.35.109.10]::call vmDestroy with ('ac687a24-05cd-
11:23:28,556::BindingXMLRPC::984::vds::(wrapper) client [127.0.0.1]::call vmCreate with ({'emulatedMachine':
11:23:39,230::BindingXMLRPC::984::vds::(wrapper) client [10.35.109.10]::call vmDestroy with ('ac687a24-05cd-
11:23:40,521::BindingXMLRPC::984::vds::(wrapper) client [127.0.0.1]::call vmCreate with ({'emulatedMachine':
11:23:51,268::BindingXMLRPC::984::vds::(wrapper) client [10.35.109.10]::call vmDestroy with ('ac687a24-05cd-
11:23:52,646::BindingXMLRPC::984::vds::(wrapper) client [127.0.0.1]::call vmCreate with ({'emulatedMachine':
12:46:07,337::BindingXMLRPC::984::vds::(wrapper) client [10.35.102.57]::call vmDestroy with ('ac687a24-05cd-

Comment 1 Greg Padgett 2013-10-25 15:39:18 UTC
Merged Change-Id: I1b73870306a559505d3441e9a2e57dfb0d191bae

Comment 3 Artyom 2013-11-01 07:47:36 UTC
How you put vm to status "Waiting for launch"?
You mean to engine vm?

Comment 4 Artyom 2013-11-04 13:34:06 UTC
Verified on ovirt-hosted-engine-ha-0.1.0-0.4.beta1.el6ev.noarch

Comment 5 Charlie 2013-11-28 01:42:03 UTC
This bug is currently attached to errata RHEA-2013:15591. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 6 Greg Padgett 2013-12-06 17:59:01 UTC
ovirt-hosted-engine-ha is a new package; does not need errata for bugs during its development.

Comment 7 errata-xmlrpc 2014-01-21 16:51:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0080.html


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