Bug 1780620
Summary: | [OSP13][tempest] smoke test fails when the external network has multiple IPv4 subnet | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Mauro Oddi <moddi> |
Component: | openstack-tempest | Assignee: | Lukas Piwowarski <lpiwowar> |
Status: | CLOSED ERRATA | QA Contact: | Martin Kopec <mkopec> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 13.0 (Queens) | CC: | apevec, ext-markku.tavasti, lhh, lpiwowar, slinaber, udesale |
Target Milestone: | --- | Keywords: | Triaged, ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-tempest-18.0.0-14.el7ost | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-24 11:41:26 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
Mauro Oddi
2019-12-06 14:36:49 UTC
*** Bug 1780619 has been marked as a duplicate of this bug. *** Hi Mauro, from what I've gathered so far, the check [1] is there for historical reasons, a few years back it just didn't work with multiple subnets, not just the tests, the whole OpenStack or something like that but that was 6 years ago. Although our official documentation states that creating a public network and one subnet is a prerequisite for running tempest tests, I think the test could be modify nowadays and done a little different way. Let me ask around and bring this topic in an upstream meeting as well to gather more info and opinions about that. Meanwhile you can use tempest cleanup [2] to remove unwanted (and leftover) subnets after test execution. [1] https://github.com/openstack/tempest/blob/ab3f72b21497bdc913cf92673d858e5767a5dd93/tempest/scenario/test_network_basic_ops.py#L349 [2] https://docs.openstack.org/tempest/latest/cleanup.html We have 2 separate subnets in our external network on purpose, and removing one of them is not option, because that would break our cloud functionality. waiting for upstream review A new tempest config option has been introduced in the Fixed in version package, subnet_id under [network] section of a tempest.conf file, which allows a user to specify the id of a subnet which is supposed to be used in case there are multiple ipv4 subnets present. In case a tested environment has multiple subnets present, network.subnet_id is set to the desired one, and at least openstack-tempest-18.0.0-14 is installed, the test is no longer failing on the ipv4 subnet mismatch. Therefore I'm marking this BZ as 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://access.redhat.com/errata/RHBA-2020:2719 |