Description of problem: The failure is: Config migration failed Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/ovirt/node/config/migrate.py", line 68, in _run migration_func() File "/usr/lib/python2.6/site-packages/ovirt/node/config/migrate.py", line 56, in importConfigs ImportConfigs().translate_all() File "/usr/lib/python2.6/site-packages/ovirt/node/config/migrate.py", line 91, in translate_all self.migrate_network_layout() File "/usr/lib/python2.6/site-packages/ovirt/node/config/migrate.py", line 320, in migrate_network_layout from ovirt.node import defaults ImportError: cannot import name defaults Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Hypervisor 6.6 (20150128.0.el6ev) How reproducible: 100% Additional info: Looks like regression in https://gerrit.ovirt.org/#/c/27303/3/src/ovirt/node/config/migrate.py
Thanks for the report and fix.
Steps to reproduce: Remove OVIRT_*VERSION parameter from the /etc/defaults/ovirt persist file and reboot the host Exception appears in /var/log/ovirt.log
I could reproduce this bug in the follow version: rhev-hypervisor6-6.6-20150128.0.iso ovirt-node-3.2.1-6.el6.noarch Test steps: 1. Clean install rhev-hypervisor6-6.6-20150128.0.iso 2. Login rhevh and press F2 to enter into shell console 3. Remove OVIRT_*VERSION parameter from the /etc/defaults/ovirt 4. persist /etc/defaults/ovirt 5. Reboot rhevh and check log info in /var/log/ovirt.log After step5, could see exception info in /var/log/ovirt.log
According comment 4, verify this bug on build rhev-hypervisor7-7.2-20151104 Versions: rhev-hypervisor7-7.2-20151104.0.iso ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch Steps: 1. Install rhev-hypervisor7-7.2-20151104 and login rhevh 2. Press F2 drop into shell, remove the OVIRT_*VERSION parameter from the /etc/defaults/ovirt 3. Persist /etc/defaults/ovirt 4. Reboot system and check log in /var/log/ovirt.log Result: There is no python ImportError error in /var/log/ovirt.log This bug has been fixed, so change the status to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0378.html