Bug 1208752 - Vdsm upgrade 3.4 >> 3.5.1 doesn't restart vdsmd service
Summary: Vdsm upgrade 3.4 >> 3.5.1 doesn't restart vdsmd service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: 3.5.1
Assignee: Yaniv Bronhaim
QA Contact: Petr Kubica
URL:
Whiteboard: infra
Depends On: 1200467
Blocks: 1193058
TreeView+ depends on / blocked
 
Reported: 2015-04-03 05:35 UTC by rhev-integ
Modified: 2016-02-10 19:43 UTC (History)
16 users (show)

Fixed In Version: vdsm-4.16.13.1-1.el6ev
Doc Type: Bug Fix
Doc Text:
Previously, when upgrading hosts from 3.4.x to 3.5.0 using 'yum update vdsm', VDSM was not restarted; as a result, the next time VDSM was restarted, it failed, and manual steps had to be performed to restore the service. Now, this issue has been resolved, and upgrading hosts from 3.4.x to 3.5.0 succeeds. Note: This issue did not apply to using the 'Reinstall' button in the Administration Portal.
Clone Of: 1200467
Environment:
Last Closed: 2015-04-28 18:52:50 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0904 0 normal SHIPPED_LIVE vdsm 3.5.1 - bug fix and enhancement update 2015-04-28 22:50:53 UTC
oVirt gerrit 39408 0 ovirt-3.5 MERGED Hack vdsm >=4.16.x for vdsm-tool import issues during upgrade Never
oVirt gerrit 39410 0 master MERGED Hack vdsm >=4.16.x for vdsm-tool import issues during upgrade Never
oVirt gerrit 39496 0 ovirt-3.5 MERGED Using vdsm-tool restore-conf in init script instead of direct call Never
oVirt gerrit 39497 0 master MERGED Using vdsm-tool restore-conf in init script instead of direct call Never

Comment 1 Petr Kubica 2015-04-14 16:04:47 UTC 
Verified in vt14.3 (vdsm-4.16.13.1-1.el7ev.x86_64)
upgrade from latest_av >> vt14.3
Comment 3 errata-xmlrpc 2015-04-28 18:52:50 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://rhn.redhat.com/errata/RHBA-2015-0904.html
Note You need to log in before you can comment on or make changes to this bug.