spack-stack on Jet platform

[BijuThomas-NOAA]

I am encountering an issue while trying to build spack-stack (using the release/1.9.0 branch and unified-dev environment) on the NOAA Jet platform within my user account.

The spack concretize step completes successfully. However, spack install fails when using the Intel compiler due to an invalid path configuration for the external [email protected] package.

The installation fails with a RuntimeError because it constructs an incorrect path for the MPI header files:

==> Error: RuntimeError: /apps/spack/spack-2024-11/linux-rocky8-x86_64/oneapi-2024.2.1/intel-oneapi-mpi-2021.13.1-d25fu74swginherkzsdbh3amrc7wu4mn/mpi/2021.13/mpi/2021.13/include does not exist

The correct location for the MPI header files is:

/apps/spack/spack-2024-11/linux-rocky8-x86_64/oneapi-2024.2.1/intel-oneapi-mpi-2021.13.1-d25fu74swginherkzsdbh3amrc7wu4mn/mpi/2021.13/mpi/include

It appears a redundant path segment (/mpi/2021.13) is being inserted during the search for the MPI header file.

Do you have any suggestions on how to resolve this path configuration issue?

compilers.yaml
packages.yaml
spack.yaml

[climbfuji]

We moved Jet from tier 1 to tier 2 when EPIC dropped support for it, see #1721. @guoqing-noaa is in charge of maintaining the site config. My suggestion is to try to update the prefix for the external MPI package definition.

[rickgrubin-noaa]

FYI re: Jet

From EPIC Program Team: "The HPC Board has decided that the Jet computing system will be decommissioned and shut down by 4/30/2026, please start thinking about alternative spaces for compute/storage and/or go ahead and remove files/data from the respective spaces on Jet. EPIC has utilized ~6% of their allocation on Jet over the last CY, with the most recent allocation usage in February 2025."