Bug 1105624

Summary:	Guest agent not configured for Autostart
Product:	[Retired] oVirt	Reporter:	Bob Doolittle <bzrh.bobd>
Component:	ovirt-guest-agent	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Belka <jbelka>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	bugs, gklein, iheim, jbelka, lveyde, rbalakri, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Windows
Whiteboard:	integration
Fixed In Version:	ovirt-guest-tools-3.5-2.iso	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:40:07 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:
Bug Depends On:	1119642
Bug Blocks:

Description Bob Doolittle 2014-06-06 14:39:07 UTC

Description of problem:

Running Windows Server 2008 R2 Enterprise

After installing ovirt-guest-tools-3.5-1.iso, service came up as expected.
Upon reboot, however it did not.

Running services.msc, I see that OVirt Guest Agent Service has "Startup Type" of "Manual".

After changing this to "Automatic", the service starts automatically upon reboot.

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

3.5-1 alpha

Steps to Reproduce:
1. Mount CD
2. Run ovirt-guest-tools-3.5-1.exe in VM
3. Reboot VM

Actual results:

Service does not start

Expected results:

Service should start automatically.


Additional info:

Comment 1 Lev Veyde 2014-06-08 09:22:03 UTC

My mistake...

I debugged it and it is due to the way Python's win32serviceutil module works.
By default the service is installed in manual mode, unless a command line option is supplied to change this behaviour (-auto).

Will fix this in the oVirt WGT installer.

Comment 2 Jiri Belka 2014-07-24 11:47:49 UTC

ovirt GT 3.5.5 has automatic for the service.

Comment 3 Sandro Bonazzola 2014-10-17 12:40:07 UTC

oVirt 3.5 has been released and should include the fix for this issue.