Bug 2229426

Summary:	UFW broken on Fedora Kinoite, as user.rules and user6.rules are not installed properly
Product:	[Fedora] Fedora	Reporter:	p8kfhpey31tl
Component:	ufw	Assignee:	Kevin Kofler <kevin>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	38	CC:	kevin, redhat-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-05 23:26:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description p8kfhpey31tl 2023-08-05 22:51:18 UTC

UFW is broken as user.rules and user6.rules are not installed properly. This bug exists since 35 and has not been fixed.

Copied from Bug 2086152:

Description of problem:

On Fedora Silverblue 36 (this also happened in Silverblue 35), ufw is broken as some files are not installed properly. I have not tried this on Fedora Workstation, so I don't know if this same issue is happening there.

Running `sudo ufw status verbose` (or any ufw command) replies with:

`ERROR: Couldn't stat '/var/lib/ufw/user.rules`

If you download the ubuntu .deb package and extract the user.rules and user6.rules files into /var/lib/ufw , ufw runs fine. For some reason, rpm-ostree is not extracting those two files into the /var/lib/ufw directory, which causes ufw to be broken and not work.

Version-Release number of selected component (if applicable):
ufw-0.35-24.fc36.noarch

Steps to Reproduce:
1. On Fedora Silverblue 36, install ufw with rpm-ostree install ufw
2. Reboot, and run sudo ufw status verbose

Actual results:

ufw is broken and fails to work.

Expected results:

ufw works, and responds with `Status: inactive`

Additional info:

Reproducible: Always

Comment 1 Kevin Kofler 2023-08-05 23:26:08 UTC


*** This bug has been marked as a duplicate of bug 2086152 ***