Feature #32238
closedBind systemd socket activation to IPv6
Description
By default foreman.socket binds to IPv4 only. This was done to make matching it in Puma easier, but it's not really what should be done in 2021 where everything should be dual stack by default.
In #31431 the need for this matching in Puma was removed which makes it much more flexible. The default should be updated.
Note that the installer currently always overrides it so it's not really a difference for most, but I want to modify the installer to rely on the default.
Given that this is not used by default, I'm setting this as a target for 2.4.1. It can't be picked to an earlier release since #31431 was merged in 2.4.0. This really is fixing something that should have been part of it.
Updated by Ewoud Kohl van Wijngaarden almost 4 years ago
- Related to Feature #29144: Run Puma using systemd socket activation added
Updated by Ewoud Kohl van Wijngaarden almost 4 years ago
- Related to Feature #31431: Use Puma 5.1's feature to synthesize systemd socket binds added
Updated by The Foreman Bot almost 4 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/foreman/pull/8421 added
Updated by Ewoud Kohl van Wijngaarden almost 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|3347fa49d500964f0209122d8d36c920d1feafcc.
Updated by The Foreman Bot over 3 years ago
- Pull request https://github.com/theforeman/foreman/pull/8432 added
Updated by The Foreman Bot over 3 years ago
- Pull request https://github.com/theforeman/foreman/pull/8433 added