Now we fixed the modularity test to try and install stream 11 (not 8) of nodejs module, a new bug is exposed: the test script is just broken, it runs into a key error when trying to install the module.

Looking at the code the problem seems to be that install_module - for some reason - calls self.suite.use_module(module, 'install', stream=None, profile=None) - it explicitly sets the stream and the profile to None when calling use_module - but the key it expects to find in the result dict that use_module returns is based on the stream and profile:

    if stream != None and profile != None:
        key = f"{module}:{stream}/{profile}"
    elif stream != None and profile == None:
        key = f"{module}:{stream}"
    else:
        key = f"{module}"
    res1 = self.suite.use_module(module, 'install', stream=None, profile=None)
    print(f"DNF installs {key} =>", res1[key])

use_module constructs the key in a similar way - though really, it'd be good to factor out key construction to a shared function - but since install_module explicitly passes it None for the stream and the module, the key use_module uses is just going to be "nodejs", while the key install_module is expecting is (as we can see) "nodejs:11".

I don't understand why install_module calls use_module in this way, actually. It was changed in 43a6e183 , but there was no explanation in that commit why it was changed to always pass None.