In rocky 9, We dont see any older OS packages, specifically kernel related packages. all the older packages are being moved to vault for archive , due to this we are unable to maintain kernel consistency among the dev and verify or prod env as we are patching the verify or prod env after 2-3 months or even later after dev env instances are patched.
How we are maintain the kernel consistency among the dev and verify or prod, It would be great if you can provide any solution for retaining the older version of kernel in the mirrorlist.
In this scenario, I would recommend considering a strategy of “promoting” repositories and updating content. For example, in pulp, each time a repository is updated, deduplication is performed in the background and each update is “versioned”. You can create automation around this to ensure there is a dev/prod set of data. There is an example discussion about it.
There are also other ways of doing this too, but would require manual work on your part if you do not wish to use pulp/foreman.
Context
Due to issues with our build system peridot, we cannot support multiple versions of packages in a repository at this time. This is stated on our version policy wiki section. This is tracked on github. There are plans to remedy this with the current build system while also working on the new storage system for peridot v2. We do not have any ETA’s at this time.