The systemd-homed.service and systemd-pstore.service are included in the preset in /usr/lib/systemd/system-preset/90-systemd.preset but they are not enabled by default on systems, excepted on Fedora CoreOS, which explicitly reset systemd configuration from the presets. I've not checked on non-rpm-ostree based systems yet. I suspect that this is because both service units are part of the systemd-udev sub-package that is not installed when the %post scriplet from the main systemd package runs the preset --all: https://src.fedoraproject.org/rpms/systemd/blob/rawhide/f/systemd.spec#_909 I've found this while working on preset-all for Silverblue as part of the unified core change: https://pagure.io/workstation-ostree-config/pull-request/246 Should we have those enabled on systems or do we want to keep them disabled for now? Reproducible: Always
Reproducible on Fedora Cloud images (which are not rpm-ostree based)
Same issue for remote-cryptsetup.target
I moved/added the scriptlets for systemd-portabled, systemd-homed, systemd-pstore, and remote-cryptsetup.target.
FEDORA-2023-48fcc26e7d has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-48fcc26e7d
FEDORA-2023-48fcc26e7d has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-b07a6a9665 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b07a6a9665
FEDORA-2023-b07a6a9665 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-b07a6a9665` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b07a6a9665 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-b07a6a9665 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
Thanks!