Bug 928275
Summary: | Post APT-update: Application or service 'BalloonService' could not be restarted | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> | ||||||||
Component: | Windows Guest Tools | Assignee: | Lev Veyde <lveyde> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | 3.2.0 | CC: | acathrow, bazulay, chetan, dfediuck, ghammer, iheim, jbelka, jkt, lbopf, lpeer, lveyde, oschreib, Rhev-m-bugs, rhod, sbonazzo, srevivo, vrozenfe, yeylon | ||||||||
Target Milestone: | --- | Keywords: | ZStream | ||||||||
Target Release: | 3.4.0 | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | integration | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: |
Previously, when upgrading from 3.1.9 via APT, an error message, "Application or service 'BalloonService' could not be restarted", appeared in the event log. Now, "BaloonService" can be restarted.
|
Story Points: | --- | ||||||||
Clone Of: | |||||||||||
: | 1067416 (view as bug list) | Environment: | |||||||||
Last Closed: | 2014-06-09 14:05:50 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: | |||||||||||
Bug Blocks: | 1067416, 1078909, 1142926 | ||||||||||
Attachments: |
|
Description
Jiri Belka
2013-03-27 09:54:35 UTC
Issue exists even when upgrading to latest 3.1 WGT - 3.1.14. (In reply to Jiri Belka from comment #1) > Issue exists even when upgrading to latest 3.1 WGT - 3.1.14. The 3.1 releases don't disable the Balloon service, like a 3.2 release. Vadim, Gal, Please read comment 9. two questions: - which build number (driver version) we use? - is it reproducible if we install the balloon service manually? Thanks, Vadim. Created attachment 872780 [details]
events
fail, 3.1.9 -> 3.4.1
Created attachment 872781 [details]
install logs
(In reply to Jiri Belka from comment #21) > Created attachment 872780 [details] > events > > fail, 3.1.9 -> 3.4.1 The reason it fails is because during the upgrade the code executed is still from the old 3.1.9 package, and not the new one, which code was fixed. The fix will appear only AFTER the first upgrade with the fixed version. To test it fixed you can upgrade to 3.3-13 (which includes the backport of the fix) and then to the 3.4-1. On the first upgrade you are supposed to see the error, but not on the second one. ok, 3.1.9->3.3.13 + apt (issue exists) ->3.4.1 + apt works as mentioned in #23. 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/RHBA-2014-0669.html |