Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1231510

Summary: Some of the neutron functional tests are failing with import error after unit test tree reorganization
Product: Red Hat OpenStack Reporter: Arie Bregman <abregman>
Component: openstack-neutronAssignee: Ihar Hrachyshka <ihrachys>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: low Docs Contact:
Priority: low    
Version: 7.0 (Kilo)CC: abregman, amuller, chrisw, ihrachys, nyechiel, tfreger, yeylon
Target Milestone: gaKeywords: OtherQA
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-2015.1.0-8.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:26:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Arie Bregman 2015-06-14 08:57:42 UTC
Description of problem:
Some of the neutron functional tests are failing with import error after unit test tree reorganization

 Traceback (most recent call last):
    ImportError: Failed to import test module: neutron.tests.functional.scheduler.test_dhcp_agent_scheduler
    Traceback (most recent call last):
      File "/usr/lib64/python2.7/unittest/loader.py", line 254, in _find_tests
        module = self._get_module_from_name(name)
      File "/usr/lib64/python2.7/unittest/loader.py", line 232, in _get_module_from_name
        __import__(name)
      File "neutron/tests/functional/scheduler/test_dhcp_agent_scheduler.py", line 24, in <module>
        from neutron.tests.unit import test_dhcp_scheduler as test_dhcp_sch
    ImportError: cannot import name test_dhcp_scheduler

Comment 5 Assaf Muller 2015-06-22 13:07:58 UTC
This was verified by Arie.

Comment 7 errata-xmlrpc 2015-08-05 13:26:28 UTC
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://access.redhat.com/errata/RHEA-2015:1548