Closed rjarry closed 2 months ago
Hi @rjarry. Thanks for your PR.
I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rjarry, slagle
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Depending on the console redirection configured on boot, logging packets before dropping them may cause excessive latency issues. Sometimes this can even stall a CPU for 200ms with some UART controllers and console=ttyS0.
In most openstack deployments, the is a bridge that may receive random DHCP requests. For example, when creating a lot of SRIOV VFs, NetworkManager will try to configure them with DHCP and broadcast packets. This causes the packets to be received by all overcloud nodes and be dropped, e.g:
I could not find any motivation for the existence of this LOG rule. Not event in puppet tripleo where this log rule was first introduced in 2015.
I think this rule has no real purpose and should be removed. There are counters for dropped packets in nftables. And if users want to know what packets are dropped, they can see them using tcpdump.
The LOG rule can be restored using the edpm_nftables_debug role variable.
Link: https://github.com/stackforge/puppet-openstack-cloud/commit/5102e5130ae4