tempest vlan test failed

Bug #1779059 reported by Itsuro Oda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-spp
Fix Released
Undecided
Itsuro Oda

Bug Description

When tempest test is run as:
"tox -e all-plugin -- networking_spp.tests.tempest.scenario --serial"
test_spp_connect_vlan failed as follows:
---
Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/usr/local/lib/python2.7/dist-packages/networking_spp/tests/tempest/scenario/test_spp.py", line 135, in test_spp_connect_vlan
        self._test_spp_connect(**net_kwargs)
      File "/usr/local/lib/python2.7/dist-packages/networking_spp/tests/tempest/scenario/test_spp.py", line 53, in _test_spp_connect
        cidr=netaddr.IPNetwork('30.0.0.0/28'))
      File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/api/base.py", line 363, in create_subnet
        raise ValueError(message)
    ValueError: Available CIDR for subnet creation could not be found
---

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-spp (master)

Fix proposed to branch: master
Review: https://review.openstack.org/578697

Changed in networking-spp:
assignee: nobody → Itsuro Oda (oda-g)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-spp (master)

Reviewed: https://review.openstack.org/578697
Committed: https://git.openstack.org/cgit/openstack/networking-spp/commit/?id=8157e571fb6ac47c7f060bb7a9966282088b1b3a
Submitter: Zuul
Branch: master

commit 8157e571fb6ac47c7f060bb7a9966282088b1b3a
Author: Itsuro Oda <email address hidden>
Date: Thu Jun 28 15:13:56 2018 +0900

    make CIDR unreserved

    This fix is necessary because create_subnet of neutron-tempest-plugin
    was changed to reserve CIDR. It is inconvenient for our test.

    Change-Id: I3fcd169399e67e729f106424ed69667aac27bf95
    Closes-Bug: #1779059

Changed in networking-spp:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.