When updating to RHEV hypervisor 20140212.1, network devices get renamed

Solution Verified - Updated -

Issue

  • When updating to RHEV hypervisor 20140212.1 or 20140213.0 network devices get renamed. For example, eth0 gets renamed as p2p1
  • The previously attached logical network becomes unattached. When re-attaching, we get the error message:
Illegal Network Parameters
  • Not all interfaces may be affected with this error
  • As a consequence, we cannot activate the hypervisor (required network not present). When reinstalling previous working version, the interface names stay the same (so hypervisor still cannot be activated)
  • In /var/log/vdsm/supervdsm.log, we see:
MainProcess|Thread-46::INFO::2014-02-18 00:07:07,188::netinfo::487::root::(_getNetInfo) Obtaining info for net eth0.
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/vdsm/netinfo.py", line 482, in _getNetInfo
  File "/usr/lib64/python2.6/site-packages/vdsm/netinfo.py", line 244, in getMtu
IOError: [Errno 2] No such file or directory: u'/sys/class/net/eth0/mtu'
  • After upgrade RHEV hypervisor we have problem with network connectivity
  • Network Issues after upgrading hypervisor from 6.5-20140212.1 to 6.5-20140213.0
  • Installing rhevh-6.5-20140217.0 on a RHEV-H host breaks all NIC connectivity.

Environment

  • Red Hat Enterprise Virtualization 3.3
  • RHEV hypervisor 20140212.1
  • RHEV hypervisor 20140213.0
  • RHEV hypervisor 20140217.0
  • RHEV hypervisor 20140407.0

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