AppStream module stream transitions between Rocky Linux 8 and 9

DNF Module Stream Consistency

Rocky Linux 8 and 9 utilize AppStream modules to provide multiple versions of the same software package. While these distributions target binary compatibility with RHEL, the default module streams may vary between minor releases or differ when transitioning from version 8 to 9.

When automating deployments across these versions, relying on default stream selection can lead to inconsistent environments if a minor release updates the default version of a critical dependency (e.g., Node.js or Python). Because major version upgrades are not supported in-place, the transition requires a clean installation where stream pinning must be explicitly defined to maintain parity.

Configuration Uncertainty

There is a need to determine the most reliable method for ensuring a specific module stream remains locked across different minor versions of Rocky Linux 9 without interfering with base system updates.

• Does pinning a stream via dnf module enable persist across minor version updates?
• What is the recommended approach to audit stream differences between a Rocky Linux 8 and 9 environment to ensure application compatibility?