Update known issue about lmod hook in host-injection

[xinan1911]

No description provided.

[casparvl]

I don't think these are two seperate issues, right? I mean #456 was about site-specific tuning in general, but it only became an 'issue' when people hit the Failed-to-modify error. Shouldn't we just add to the "Failed to modify UD QP to INIT... etc" that the OMPI_MCA_* environment variables can be done in host_injections/...?

I was browsing the docs, I think we should have some general explaination of host_injections under Advanced usage. I.e. that this directory is used for site specific tuning. And then, in a paragraph there, we can add how it can be used to execute LMOD hooks for site specific tuning. We can give an example there of a hook (might as well use the example of setting these three OpenMPI environment variables). It's a good point, I wanted to make this documentation, but didn't get to it before my leave. Writing it as a todo for this afternoon... We can then refer to that from the "Failed to modify UD QP to INIT" known issue and give the code for the LMOD hook that can be used as a workaround for this particular issue.

[casparvl]

Docs PR for Lmod hooks made here. I'd simply put an example hook to resolve this issue under the existing Failed to modify UD QP to INIT on mlx5_0: Operation not permitted header, and reference the new docs on Lmod hooks for further information.

[xinan1911]

@casparvl Adjusted on the known issues pages. Could you review it and if everything is okay, merge it?

[laraPPr]

@xinan1911 could you also look at mkdocs.yml ? because the menu now has v2022/02 and pilot but their are no know issues on those repositories and no pages for those repos.

[xinan1911]

@xinan1911 could you also look at mkdocs.yml ? because the menu now has v2022/02 and pilot but their are no know issues on those repositories and no pages for those repos.

Adjusted! Those pages are removed in the mkdocs

[laraPPr]

@Xin the CI is failing because you behind on main

[xinan1911]

@Xin the CI is failing because you behind on main

@laraPPr
The build error message shows

INFO    -  Doc file 'test-suite/ReFrame-configuration-file.md' contains a link '#RFM_CONFIG_FILES', but there is no such anchor on this page.

INFO    -  Doc file 'test-suite/ReFrame-configuration-file.md' contains a link '#RFM_PREFIX', but there is no such anchor on this page.

INFO    -  Doc file 'test-suite/installation-configuration.md' contains a link '#reframe-config-file', but there is no such anchor on this page.

INFO    -  Doc file 'test-suite/installation-configuration.md' contains a link '#logging', but there is no such anchor on this page.

INFO    -  Doc file 'test-suite/release-notes.md' contains a link 'installation-configuration.md#reframe-config-file', but the doc 'test-suite/installation-configuration.md' does not contain an anchor '#reframe-config-file'.

INFO    -  Doc file 'test-suite/release-notes.md' contains a link 'installation-configuration.md#logging', but the doc 'test-suite/installation-configuration.md' does not contain an anchor '#logging'.

INFO    -  Doc file 'test-suite/release-notes.md' contains a link 'installation-configuration.md#partitions', but the doc 'test-suite/installation-configuration.md' does not contain an anchor '#partitions'.

INFO    -  Doc file 'test-suite/release-notes.md' contains a link 'usage.md#gromacs', but the doc 'test-suite/usage.md' does not contain an anchor '#gromacs'.

INFO    -  Doc file 'test-suite/release-notes.md' contains a link 'usage.md#tensorflow', but the doc 'test-suite/usage.md' does not contain an anchor '#tensorflow'.

INFO    -  Doc file 'test-suite/usage.md' contains a link '#Configuring-ReFrame', but there is no such anchor on this page.

INFO    -  Doc file 'test-suite/usage.md' contains a link 'installation-configuration.md#logging', but the doc 'test-suite/installation-configuration.md' does not contain an anchor '#logging'

Caspar has already fixed these in his PR https://github.com/EESSI/docs/pull/188/files#diff-679f410211edd9a310548400e25680c354062d32ab8a7df0c963d42ac85d2da8 which hasn't been merged yet. Maybe his PR can be merged first before this PR.

[laraPPr]

I was referring to these warnings

WARNING -  A reference to 'available_software/overview.md' is included in the 'nav' configuration, which is not found in the documentation files.
WARNING -  A reference to 'getting_access/eessi_wsl.md' is included in the 'nav' configuration, which is not found in the documentation files.
WARNING -  A reference to 'getting_access/eessi_limactl.md' is included in the 'nav' configuration, which is not found in the documentation files.

[casparvl]

Looks good to me!