Add a top-lever dir init/modules/EESSI containing a symlink to the 2023.06 modulefile

[bedroge]

Tested it in a transaction that I aborted/didn't publish, this is the result:

[bob@multixscale-stratum0 ~]$ sudo ls -lR /cvmfs/software.eessi.io/init
/cvmfs/software.eessi.io/init:
total 0
drwxr-xr-x. 3 root root 19 Sep  5 13:24 modules

/cvmfs/software.eessi.io/init/modules:
total 0
drwxr-xr-x. 2 root root 25 Sep  5 13:24 EESSI

/cvmfs/software.eessi.io/init/modules/EESSI:
total 0
lrwxrwxrwx. 1 root root 72 Sep  5 13:24 2023.06.lua -> /cvmfs/software.eessi.io/versions/2023.06/init/modules/EESSI/2023.06.lua

[boegel]

@bedroge I was checking how we populated /cvmfs/software.eessi.io/init/modules/EESSI, and it seems that done by the changes in this PR, which never got merged?

[bedroge]

@bedroge I was checking how we populated /cvmfs/software.eessi.io/init/modules/EESSI, and it seems that done by the changes in this PR, which never got merged?

Yes, I think that's correct, though I did publish the thing in the end. So would be good to still merge this.

[boegel]

For EESSI 2025.06, we want to create a symlink as well, and (for now) an additional .modulerc.lua file (in /cvmfs/software.eessi.io/init/modules) that contains:

-- hide EESSI/2025.06 module until software layer has enough installations in it
hide_version("EESSI/2025.06")

[boegel]

For EESSI 2025.06, we want to create a symlink as well, and (for now) an additional .modulerc.lua file (in /cvmfs/software.eessi.io/init/modules) that contains:

-- hide EESSI/2025.06 module until software layer has enough installations in it
hide_version("EESSI/2025.06")

@bedroge This will need to be done to start building out software layer for EESSI 2025.06, since the EESSI/2025.06 module is loaded by the install script (and it comes from /cvmfs/software.eessi.io/init/modules/...

So I took a stab at it (totally untested): bedroge#4

[bedroge]

This needs EESSI/software-layer-scripts#6 to be merged first.

[bedroge]

Tested this by running the playbook and without publishing the transaction:

$ ls /cvmfs/software.eessi.io/init/modules/EESSI/ -la
total 5
drwxr-xr-x. 1 root root  42 Jul  2 11:51 .
drwxr-xr-x. 1 root root  19 Sep  5  2024 ..
lrwxrwxrwx. 1 root root  72 Sep  5  2024 2023.06.lua -> /cvmfs/software.eessi.io/versions/2023.06/init/modules/EESSI/2023.06.lua
lrwxrwxrwx. 1 root root  72 Jul  2 11:50 2025.06.lua -> /cvmfs/software.eessi.io/versions/2025.06/init/modules/EESSI/2025.06.lua
-rw-r--r--. 1 root root 111 Jul  2 11:51 .modulerc

$ cat /cvmfs/software.eessi.io/init/modules/EESSI/.modulerc 
-- hide EESSI/2025.06 module until software layer has enough installations in it
hide_version("EESSI/2025.06")

Looks good to me. The 2025.06 symlink is still broken, because we need EESSI/software-layer-scripts#6 to be deployed first.

[bedroge]

Gave it a try in a container, apparently the .modulerc file needs to have a .lua extension:

Apptainer> ml av

------------------------------------------------ /cvmfs/software.eessi.io/init/modules -------------------------------------------------
   EESSI/2023.06    EESSI/2025.06 (D)


Apptainer> mv .modulerc .modulerc.lua
Apptainer> ml av

------------------------------------------------ /cvmfs/software.eessi.io/init/modules -------------------------------------------------
   EESSI/2023.06 (D)

So I changed that in the vars file.

[casparvl]

Ansible Lint failure is being resolved in #229 , we'll ignore it in this PR.

[bedroge]

Created an issue for the other failing CI: #234.

[casparvl]

Discussed this PR in a meeting with Bob. Looks good to me. The two CI failures appear to be unrelated. One already has another PR to fix it, the other will be raised in an issue by Bob. But the fact that the same workflow succeeds for Ubuntu 20.X and Rocky 8 suggests the issue is something with the VM image for Ubuntu 22.X that specifically causes this failure. Again: unrelated to this PR, and we don't want to block this, so approved!