Bug 2086152

Summary:	UFW broken on Fedora Silverblue, as user.rules and user6.rules are not installed properly
Product:	[Fedora] Fedora	Reporter:	core_contingency <ccontingency>
Component:	ufw	Assignee:	Kevin Kofler <kevin>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	38	CC:	kevin, p8kfhpey31tl, redhat-bugzilla
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-25 17:20:12 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 core_contingency 2022-05-14 08:09:38 UTC

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:

Comment 1 Ben Cotton 2023-04-25 17:09:46 UTC

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Ludek Smid 2023-05-25 17:20:12 UTC

Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

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

*** Bug 2229426 has been marked as a duplicate of this bug. ***

Comment 4 Robert Scheck 2023-08-06 13:26:19 UTC

From my point of view this is specific to Silverblue (this issue does not exist on regular Fedora systems) and nothing which can be fixed in ufw.