Red Hat Bugzilla – Bug 1290372
After upgrading vdsm rpms from 3.3 or 3.4 to 3.6, vdsm fails to restart because it's not configured
Last modified: 2016-02-18 06:12:30 EST
Description of problem:
After upgrading vdsm rpms from 3.3 or 3.4 to 3.6, vdsm fails to restart:
To fix is necessary to manually run:
vdsm-tool configure --force
Version-Release number of selected component (if applicable):
upgrading from vdsm-4.13 or 4.14 to vdsm-4.17
Steps to Reproduce:
1. deploy the host with 3.3 or 3.4 repo
2. add 3.6 repo
3. yum update
4. VDSM will not restart
VDSM will not restart after yum update because multipath and passwd are not configured
Multipath and passwd should be configured during upgrade.
How multipath is not configured after upgrading an existing setup?
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Fixed bug tickets must have target milestone set prior to fixing them. Please set the correct milestone and move the bugs back to the previous status after this is corrected.
oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA
working on vdsm-4.17.18-0.el7ev.noarch