After upgrading a host during a RHEV 3.4 to 3.5 upgrade, it cannot be activated as VDSM fails to start
Issue
-
After upgrading a host during a RHEV 3.4 to 3.5 upgrade, the host cannot be activated.
-
The
vdsmdservice fails to restart. -
The
messagesfile on the host contains;
Jun 10 09:25:52 host-A python: module upgrade_300_networks could not load to vdsm-tool: Traceback (most recent call last):#012 File "/usr/bin/vdsm-tool", line 81, in load_modules#012 mod_absp, mod_desc)#012 File "/usr/lib64/python2.6/site-packages/vdsm/tool/upgrade_300_networks.py", line 30, in <module>#012 from netconf import ifcfg#012ImportError: No module named netconf
Environment
- Red Hat Enterprise Virtualization (RHEV) 3.5
- Red Hat Enterprise Linux (RHEL) 6.6 host
- VDSM
vdsm-4.16versions prior tovdsm-4.16.13.1-1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.