After upgrading a host during a RHEV 3.4 to 3.5 upgrade, it cannot be activated as VDSM fails to start

Solution Unverified - Updated -

Issue

  • After upgrading a host during a RHEV 3.4 to 3.5 upgrade, the host cannot be activated.

  • The vdsmd service fails to restart.

  • The messages file 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.16 versions prior to vdsm-4.16.13.1-1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content