The Fedora 45 installer test week is open through October 2, giving users a short window to try three notable Anaconda changes before the next release. Fedora’s QA team wants reports from people who can test on a virtual machine or spare computer. This is a chance to catch installation problems while the release is still in development, rather than after the final images ship.
Three installer changes need attention
According to the Fedora Community Blog’s test-week announcement, this round centers on broader WebUI support, remote installation, and Stratis storage. These are meaningful changes for people who deploy Fedora in different environments.
- Atomic desktops: The web-based installer now covers Fedora Silverblue and Kinoite, along with several other Atomic variants.
- Remote WebUI: A tester can drive the installation from a browser on another device.
- Stratis: The WebUI can configure Stratis storage during installation.
Each feature touches a different part of the install path. The remote option matters when a machine has limited local input or display access. Stratis matters to users who want managed storage without assembling every layer by hand. Atomic desktop support broadens the same installer experience across Fedora editions.
What Stratis testers should check
Fedora’s Stratis installer walkthrough explains that a pool can sit on one or more devices, with filesystems built on that pool. It also notes limits: Anaconda does not currently set up caching or passphrase-free encryption during installation. Testers should therefore compare the choices the installer offers with the storage layout they actually need. Do not treat the new option as a promise that every Stratis feature is already available in the installer.
How to take part before the window closes
The QA team recommends the latest Fedora 45 nightly image on a virtual machine or spare hardware, not a production system or a device holding important data. Its test-day page links to test cases and results. Record the image you used, the installation path you chose, and any error that appeared. That detail helps developers reproduce a problem.
Fedora has been inviting targeted testing across the release cycle. Our earlier look at the Fedora CoreOS 45 test week covered a separate effort focused on that edition. The current Anaconda event is about the installer itself, so a successful desktop boot alone is not the whole test.
As of October 1, there is still time to submit useful findings before the October 2 deadline. If an install fails, keep the logs and report the precise step. If it succeeds, a recorded result is valuable too: it shows which combinations of hardware, edition, and storage passed during the Fedora 45 installer test week.