Inconsistent behaviour of the `status` command
I tested the status
command in a state where one toolchain was installed for broadwell (bigmam) and three lmod directories were present for sandybrigde (login) but no spack directory (currently usually a symlink to Ashwin's test installations) was present.
The mpsd-software status <release>
reports different results on the login nodes and on the bigmem nodes.
bigmem:
mpsddeb@mpsd-hpc-hp-002:/opt_mpsd/linux-debian11$ mpsd-software --version
2023.9.21
mpsddeb@mpsd-hpc-hp-002:/opt_mpsd/linux-debian11$ mpsd-software status
Installed MPSD software releases:
dev-23a
23b
mpsddeb@mpsd-hpc-hp-002:/opt_mpsd/linux-debian11$ mpsd-software status 23b
Installed toolchains (23b):
- broadwell
foss2022a-serial
[module use /opt_mpsd/linux-debian11/23b/broadwell/lmod/Core]
- sandybridge
foss2021a-serial
foss2022a-mpi
foss2021a-mpi
foss2022a-serial
[module use /opt_mpsd/linux-debian11/23b/sandybridge/lmod/Core]
mpsddeb@mpsd-hpc-hp-002:/opt_mpsd/linux-debian11$
login:
mpsddeb@mpsd-hpc-login1:/opt_mpsd/linux-debian11$ mpsd-software --version
2023.9.21
mpsddeb@mpsd-hpc-login1:/opt_mpsd/linux-debian11$ mpsd-software status
Installed MPSD software releases:
dev-23a
23b
mpsddeb@mpsd-hpc-login1:/opt_mpsd/linux-debian11$ mpsd-software status 23b
[08:48:45] ERROR MPSD release '23b' has not been completely installed. mpsd_software.py:1332
mpsddeb@mpsd-hpc-login1:/opt_mpsd/linux-debian11$
Additional details from @akarnad:
thats a small inconsistency in the enforcement of the tool. the tool wants to prevent the calling of the status command when the spack folder isnt completely installed ( this helps when asking for status toolchain as then you wont get subprocess error due to lack of spack) but this check is done only for the current microarch. once the test passess, the tool prints all available toolcahins (for all microarch)
probably a good idea to only test for spack-environments when asking status of a release and then test for spack only when asking for status of a toolchains