On an existing F42 installation. sudo dnf install nftables systemctl enable nftables.service reboot and verify nftables.service is still active. systemctl status nftables Perform the upgrade to F43. After the upgrade is completed verify status of the nftables service. systemctl status nftables Same is not observed if you upgrade to F44. Workaround is to enable the service post upgrade. systemctl enable nftables Reproducible: Always Steps to Reproduce: 1.Install nftables and enable the service on an existing F42 installation 2.Upgrade to F43 3.Observe nftables service is disabled. Actual Results: nftables service is disabled Expected Results: nftables service is enabled since the user had previously enabled it. Additional Information: Believe this is due to https://src.fedoraproject.org/rpms/nftables/c/a29ebf548f74b44d259a113ba72e03e8b18c1c80?branch=main where the service was split out into it's own package. Since it is an initial install it is handled based on the Fedora presets.
I guess neither myself or Phil had this one on our radar. ;( Sorry about that. Yes, I think its due to the service moving to another package and using the initial state there. I'm not fully sure of the best solution. Possibly we can just add it to presets (There are no rules by default, so it's just a noop) but that means it shows as enabled when lots of people aren't using it. Or some more complex scriptlets to see if we can tell if the old one was enabled on new install? Adding system maintainer for input.
Can you do something like this in in post ... %if %(systemctl -q is-enabled nftables.service) systemctl enable nftables.service %else %systemd_post nftables.service %endif
(In reply to grumpey0 from comment #2) > Can you do something like this in in post ... > > %if %(systemctl -q is-enabled nftables.service) > systemctl enable nftables.service > %else > %systemd_post nftables.service > %endif No that I think about I don't think this will work. Apologies for the noise.
%post services if [ $1 -eq 1 ] && [[ -h /etc/systemd/system/multi-user.target.wants/nftables.service ]]; then echo "nftables.service is already enabled" else %systemd_post nftables.service fi This looks like it works testing from the everything iso in a VM.
So, does that work for the dist upgrade case tho? ie, you have a f42 install with nftables enabled and then dist-upgrade to f43...
It did using a COPR,https://copr.fedorainfracloud.org/coprs/grumpey/nftables-test/ With the 42 everything iso, and doing a dnf system-upgrade download and dnf offline reboot.
humf. Well, I don't really like that, but it seems the least bad way to do it. So, thanks for that... I adjusted it some and submitted a PR on it ( https://src.fedoraproject.org/rpms/nftables/pull-request/6 ) Can you test this one?
FEDORA-2026-9ff8265724 (nftables-1.1.3-6.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-9ff8265724
FEDORA-2026-9ff8265724 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-9ff8265724` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-9ff8265724 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-9ff8265724 (nftables-1.1.3-6.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.