Browse Source

Fix IPv6 cidr used by public network in tempest-slow job

Same issue was fixed in tempest in [1] but it isn't in tempest 26.0.0
so when tempest was pinned to that version in stable/stein jobs, it
started failing with the error like described in [2].

This patch makes the same fix as was done in Tempest but in Neutron repo
for stable/stein job only.

[1] https://review.opendev.org/c/openstack/tempest/+/774764
[2] https://bugs.launchpad.net/neutron/+bug/1914037

Change-Id: I0aca489715ddd0da97036e75c5c4265b713c19b8
changes/89/777389/3
Slawek Kaplonski 2 months ago
parent
commit
3bec05e90f
1 changed files with 14 additions and 0 deletions
  1. +14
    -0
      .zuul.yaml

+ 14
- 0
.zuul.yaml View File

@ -49,6 +49,13 @@
irrelevant-files: *tempest-irrelevant-files
- tempest-slow-py3:
irrelevant-files: *tempest-irrelevant-files
vars:
devstack_localrc:
# to avoid https://bugs.launchpad.net/neutron/+bug/1914037
# as we couldn't backport the fix to stein release
IPV6_PUBLIC_RANGE: 2001:db8:0:10::/64
IPV6_PUBLIC_NETWORK_GATEWAY: 2001:db8:0:10::2
IPV6_ROUTER_GW_IP: 2001:db8:0:10::1
- networking-ovn-tempest-dsvm-ovs-release:
voting: false
irrelevant-files: *tempest-irrelevant-files
@ -73,6 +80,13 @@
timeout: 10800
- tempest-slow-py3:
irrelevant-files: *tempest-irrelevant-files
vars:
devstack_localrc:
# to avoid https://bugs.launchpad.net/neutron/+bug/1914037
# as we couldn't backport the fix to stein release
IPV6_PUBLIC_RANGE: 2001:db8:0:10::/64
IPV6_PUBLIC_NETWORK_GATEWAY: 2001:db8:0:10::2
IPV6_ROUTER_GW_IP: 2001:db8:0:10::1
- grenade-py3:
irrelevant-files: *tempest-irrelevant-files
periodic:


Loading…
Cancel
Save