Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1580489

Summary:	WGT sometimes fails to run after reboot
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Petr Matyáš <pmatyas>
Component:	rhev-guest-tools	Assignee:	Lev Veyde <lveyde>
Status:	CLOSED ERRATA	QA Contact:	Petr Matyáš <pmatyas>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.2.3	CC:	bugs, dfediuck, eheftman, lsvaty, lveyde, sbonazzo, ylavi
Target Milestone:	ovirt-4.2.5	Keywords:	Automation, AutomationBlocker, Regression, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhv-guest-tools-iso-4.2-7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-31 17:51:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Matyáš 2018-05-21 15:16:16 UTC

Description of problem:
On some systems (e.g. W8.1 32b) in like 20% of time service oVirt Agent fails to run and can't be started manually after reboot (also it was not reporting all the data correctly before the reboot).
This is happening in our automation but I currently have one running system exhibiting this issue and can provide access to it.

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

How reproducible:
20%

Steps to Reproduce:
1. install WGT in a windows system
2. reboot the VM
3.

Actual results:
agent fails to run

Expected results:
agent service is running correctly

Additional info:

Comment 14 Emma Heftman 2018-07-24 10:33:40 UTC

Hey Lev. Does this bug need doc text? If not please change the requires_doc_text flag to -.
Thanks

Comment 15 Petr Matyáš 2018-07-26 08:05:33 UTC

Verified on rhv-guest-tools-iso-4.2-7.el7ev.noarch

Comment 17 errata-xmlrpc 2018-07-31 17:51:17 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.

https://access.redhat.com/errata/RHEA-2018:2327