Skip to content

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Apr 3, 2023

This PR contains a snapshot of yoga from upstream.

ralonsoh and others added 6 commits March 16, 2023 16:28
This patch is a partial revert of [1], reinstantiating the code merged
in [2]. This patch is the complementary to [1]: the traffic with
custom ethertypes is allowed in the ingress processing tables, same
as [1] is allowing all traffic from the virtual machine ports in this
host to leave the node. Both, this patch and [1], are bypassing the
OVS firewall just for the traffic with the configured allowed
ethertypes and just for/to the local ports and MAC addresses.

Any other traffic not coming from a local port or with destination
a local port, will be blocked as is now.

[1]https://review.opendev.org/c/openstack/neutron/+/678021
[2]https://review.opendev.org/c/openstack/neutron/+/668224/

Conflicts:
       doc/source/admin/config-ovsfwdriver.rst
       neutron/tests/unit/agent/linux/openvswitch_firewall/test_firewall.py

Closes-Bug: #2009221
Related-Bug: #1832758
Change-Id: Ib8340d9430b946a446edf80886c49fbac729073c
(cherry picked from commit 008277b)
(cherry picked from commit 5026d805fe01aaf237081c606f1d1bf87bbff6d4)
When networks are created using REST APIs, if the MTU isn't specified
in the request, then a default value of 0 is used. Some use cases, such
as the auto-allocated-topology workflow, call the plugin directly to
create networks, bypassing the layer that inserts this default value.
Commit 6862568 introduced a different
default value at the DB layer, defined by a constant in neutron-lib.
If the maximum MTU size has been configured lower than this constant,
then the user receives an exception, even though they didn't provide
a value for MTU.

This patch changes the default value used in the DB layer, so that
it's consistent with the workflow seen via REST APIs.

Change-Id: Ica21e891cd2559942abb0ab2b12132e7f6cdd835
Closes-Bug: #1896933
(cherry picked from commit f759915)
The metadata port fixed IPs depend on the subnets "enabled_dhcp" flag.
If the subnet has this flag disabled, the metadata port doesn't receive
an IP on the subnet CIDR.

The method ``create_metadata_port`` should explicitly define what fixed
IPs should request the metadata port during the creating depending on
the subnets "enabled_dhcp" flag.

Closes-Bug: #2011724
Change-Id: If362fab20ac03f8b62471b60c031f9349171ce93
(cherry picked from commit 9704dca)
This reverts commit f83a97d.

Reason for revert:
As part of the reverted commit, the redirect-type=bridged flag was
enabled by default. However this have the side effect of also
decentralizing N/S traffic for geneve tenant networks, breaking the
VM connectivity on them when it must be centralized, i.e., when no
FIPs are associated to the VMs.

A new fix will be provided ASAP.

Change-Id: I258cc439c70cfeae5b638ddd8e650dc2bf403c31
@github-actions github-actions bot requested a review from a team as a code owner April 3, 2023 08:23
@github-actions github-actions bot added automated Automated action performed by GitHub Actions synchronisation labels Apr 3, 2023
@markgoddard markgoddard merged commit eb4bd1a into stackhpc/yoga Apr 3, 2023
@markgoddard markgoddard deleted the upstream/yoga-2023-04-03 branch April 3, 2023 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated Automated action performed by GitHub Actions synchronisation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants