We have to check F36 changes regarding their potential specific impact on Fedora Server.
F36 Change Set: https://fedoraproject.org/wiki/Releases/36/ChangeSet
Bugs: [Bug 2009731] Fedora 35: Server boot x86_64 image exceeds maximum size [Bug 1963007] Fedora 35: Server boot armhfp image exceeds maximum size
Adam Williamson is working on
Changes with known potential specific impact
F36 Change: Relocate RPM database to /usr (System-Wide Change proposal)
F36 Change: DIGLIM (System-Wide Change proposal)
F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)
F36 Change: Users are administrators by default in the installer GUI. (Self-Contained Change proposal)
F36 Change proposal: No ifcfg by default (Self-Contained Change)
Metadata Update from @pboy: - Issue tagged with: meeting
These are the accepted changes that I think we might want to look at:
We should track:
Bug 2032085
It breaks among others split DNS, important for virtualization.
Metadata Update from @pboy: - Issue status updated to: Closed (was: Open)
Obviously, I closed this although unintentional. So I re-open it.
Metadata Update from @pboy: - Issue status updated to: Open (was: Closed)
After Change set is fixed (kind of) we have:
== Changes ==
(1) Ansible 5 - major update (2) Cockpit Filesharing - new (3) DNS Over TLS - possible conflicts with existing configurations
(4) java17-openjdk as system JDK - given that FreeIPA etc is based on JDK - various issues as discussed on mailing list
(5) No ifcfg by default only if it survives beta, otherwise defered to F37 see FESCo 2022-03.01 (6) PostgreSQL 14 - possible conflicts with existing configurations (7) openldap upgrade (8) Users are administrators by default in Install GUI - does it work as expected - No side effects
== Known Issues ==
(9) systemd-resolved - /etc/resolv.conf not a link - breaks split DNS with libvirt internal network
List as in comment directly above was decided at IRC meeting 2022-03-02 and incorporated into a list of tasks/tests to be completed (#64). Issue closed.
Metadata Update from @pboy: - Issue untagged with: meeting
Log in to comment on this ticket.