Bug 1717094

Summary:	Configuration file netdev-ingress.nft is missing
Product:	Red Hat Enterprise Linux 8	Reporter:	Gabríel Arthúr Pétursson <gabriel.arthur.petursson>
Component:	nftables	Assignee:	Phil Sutter <psutter>
Status:	CLOSED ERRATA	QA Contact:	Jiri Peska <jpeska>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	rkhan, todoleza
Target Milestone:	rc
Target Release:	8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	nftables-0.9.0-10.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:36:21 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 Gabríel Arthúr Pétursson 2019-06-04 16:53:21 UTC

Description of problem:

The file netdev-ingress.nft is missing from /etc/nftables/. It is included by /etc/nftables/all-in-one.nft.


Version-Release number of selected component (if applicable):

RHEL 8.0 (Ootpa)
nftables-1:0.9.0-8.el8.x86_64


How reproducible:

Always.


Steps to Reproduce:
1. cd /etc/nftables
2. nft -f all-in-one.nft


Actual results:

[root@proclidev03 nftables]# nft -f /etc/nftables/all-in-one.nft 
/etc/nftables/all-in-one.nft:18:1-31: Error: File not found: ./netdev-ingress.nft
include "./netdev-ingress.nft"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


Expected results:

The firewall rules should apply normally.

Comment 1 Phil Sutter 2019-06-24 15:19:41 UTC

The missing configuration file is present in examples/ directory of upstream release tarball, so only a spec file change is required.

Tomas, please provide qa_ack+. This is a non-functional change (all include statements to sample configs are commented by default). For testing, making sure /etc/nftables/netdev-ingress.nft exists should suffice.

Comment 7 errata-xmlrpc 2019-11-05 22:36:21 UTC

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/RHEA-2019:3659