-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate existing systems to iptables-nft
and remove iptables-legacy
#1818
Comments
Hum, we'll also likely have to remove / migrate On my Atomic Desktops I also have:
which apparently got set up on first boot. Will have to investigate. |
On the Atomic Desktops side of things: https://gitlab.com/fedora/ostree/sig/-/issues/51 |
Suggested paths: Option A:
Pseudo bash code:
Option B:
Pseudo bash code:
My preference goes to option B. |
For the Atomic Desktops, I'll probably write a script that removes |
This makes sure that the system is setup properly and that the migration script will do the right thing on older systems. See: coreos/fedora-coreos-tracker#1818 See: coreos/fedora-coreos-tracker#677 See: https://docs.fedoraproject.org/en-US/fedora-coreos/alternatives/
I've created https://gitlab.com/fedora/bootc/tracker/-/issues/44 on the bootc side of things. |
B looks good to me. Though.. I have a few questions:
|
Describe the enhancement
Since #676 (in stable
36.20220505.3.2
), we've moved to the nft backend for iptables by default, but as far as I remember / could figure out, we did not update existing systems to it.We now have proper support for alternatives on ostree based systems (fedora-sysv/chkconfig#135 & #677) so we can use that to migrate users at boot time.
Then we should remove the legacy package.
Unfortunately we can not just drop our manual workaround to migrate systems to the nft backend as they have the same priority set in their alternatives config:
So we'll have to run a script via a systemd unit to do it:
As this could potentially be a breaking change, we might want to do it only starting with Fedora 42.
System details
N/A
Additional information
See:
The text was updated successfully, but these errors were encountered: