Python Module Stream Default Change in AlmaLinux 9.4 and Its Effect on Kickstart Provisioning

Short Answer

Yes, the AlmaLinux 9.4 installer will result in the python:3.11 stream being active, but not because the installer "enables" it. The default stream is defined in the AppStream repository metadata. When a Kickstart file omits a specific module directive, dnf resolves the python package to whatever stream the repository marks as default—which, in AlmaLinux 9.4, is 3.11. Consequently, a Kickstart installation and a generic minimal installation using the same 9.4 repositories will converge on the same version.

Likely Explanation vs. Confirmed Facts

Confirmed: Module defaults are stored in the repository's metadata (modules.yaml). The installer (Anaconda) uses dnf to resolve dependencies; if no stream is specified, dnf follows the metadata's default. This is consistent across all installation methods.

Likely Explanation for Divergence: If you observe different Python versions between a minimal install and a Kickstart install, it is likely due to repository mismatch rather than installer logic. Potential causes include:

• Stale Mirrors: An internal mirror serving 9.3 metadata (where the default was 3.9) while the minimal install uses official 9.4 mirrors.
• Version-Pinned Repos: A url or repo directive in the Kickstart pointing to a specific snapshot or older release.
• Boot Media Mismatch: Using a 9.3 boot ISO while pointing to 9.4 repositories, which can occasionally lead to unexpected resolution behavior.

Locking the Stream for Reproducibility

To guarantee identical versions regardless of the repository's default state, explicitly declare the stream in the main section of your Kickstart file:

module --name=python --stream=3.11

This ensures that even if the system is provisioned against a 9.3 mirror or a future 9.5 mirror with a different default, the 3.11 stream is forced. For existing systems, you can converge the version via %post or configuration management:

dnf -y module enable python:3.11
dnf -y distro-sync

The distro-sync command is critical here to ensure any packages installed from a previous stream are upgraded or replaced to match the newly enabled stream.

Verification and Constraints

Verify the active stream and interpreter on the provisioned host:

dnf module list python
python3 --version

In the output of dnf module list, [d] indicates the repository default and [e] indicates the enabled stream. For a locked environment, 3.11 should be marked [e].

Important Constraints

• Platform Python: The system's internal interpreter (/usr/libexec/platform-python) is separate from the AppStream module and is not affected by these changes.
• Anaconda Version: The module command in Kickstart requires a compatible version of Anaconda; verify this against the specific boot media used in your pipeline.

If divergence persists after pinning, the one diagnostic detail required to change this recommendation is the specific AppStream repository URL used by the Kickstart process.