Failed to resolve module stream in dnf module

Answer the question first

When dnf module … prints Failed to resolve module stream, the resolver cannot locate the requested module metadata in the enabled AppStream repositories. The message itself does not reveal whether the module name, stream, or context/profile is missing.

What diagnostic detail to surface?

Run dnf --debug module info : or dnf -v module list . The debug trace will contain a line such as:

• module not found – the module name is not present in any enabled repo.
• stream not found – the module exists, but the requested stream does not.
• context not found – the module and stream exist, but the requested context/profile is absent.

Using the debug output allows you to pinpoint exactly which component is missing.

Is module‑stream support still provided for CentOS 8?

CentOS 8 reached end‑of‑life on 2021‑12‑31. After that date no official updates, including AppStream module‑stream metadata, are published for CentOS 8. Consequently, continued module‑stream support is not defined or guaranteed. The DNF project has not announced a default‑stream fallback for CentOS 8; a stream must be specified explicitly or a default stream must exist in the repository metadata.

Practical steps for this case

1. Refresh the repository cache to ensure you’re working with the latest metadata:

   dnf clean all
   sudo dnf makecache
   

2. Verify that the module’s metadata is present locally:

   ls /var/cache/dnf/*/modules | grep -i <module-name>
   

3. Run the debug command to see which part is missing:

   dnf --debug module info <module-name>:<stream>
   

4. If the module is absent, enable or add an AppStream repo that contains it. If the stream is absent, install a different stream or request the required stream from the upstream project.

5. As a workaround on a legacy system, disable modularity for the package:

   dnf install --nobest <package>
   

6. Consider migrating to CentOS Stream or another supported distribution where module streams continue to receive updates.

Missing diagnostic detail that would change the recommendation

Could you confirm whether the AppStream repository you are using still hosts the module metadata for the requested stream? If the repo is no longer maintained, the only viable path is to switch to a supported stream or distribution.

Summary

Use dnf --debug to pinpoint whether the module name, stream, or context is missing. CentOS 8 no longer receives module‑stream updates, and no default‑stream fallback is planned. Workarounds include disabling modularity or migrating to a supported release.