Description of problem: In bug #1557735 we recognized case where vdsmd is being restarted during upgrade and fails to start. We are not sure exactly if this flow is right or wrong, but in case it happens vdsmd stays down after upgrade. In this bugzilla we add logic to remember vdsmd status before starting the upgrade and re-establish same state after upgrade is done. This change is done as part of the rpm spec and related to vdsm packaging. Version-Release number of selected component (if applicable): v4.20.23 Actual results: Vdsm stays with same status after upgrade (stopped or started) Additional info: This flow requires verification for upgrades scenarios to latest vdsm build
Severity?
We don't have regressions so far. It will be critical if vdsm introduces new config values, but as far as 4.2 we don't have it between recent versions.
3.6 -> 4.2.4 upgrade OK 4.1 -> 4.2.4 upgrade OK ( tested with stopped and also with started vdsm - status was OK in both cases )
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.