You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As reported in the EESSI support portal issue #25, curl fails in RHEL 8 and above systems as CA files location differs. Works for all rhel based systems as I could reproduce the issue also in them.
$ cat /etc/os-release
NAME="Rocky Linux"
VERSION="9.3 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
$ source software-layer/init/bash
Found EESSI repo @ /cvmfs/software.eessi.io/versions/2023.06!
archdetect says x86_64/intel/skylake_avx512
Using x86_64/intel/skylake_avx512 as software subdirectory.
[...]
Environment set up to use EESSI (2023.06), have fun!
{EESSI 2023.06} $ ml CMake
{EESSI 2023.06} $ curl https://www.example.com
<!doctype html>
<html>
<head>
<title>Example Domain</title>
[...]
I am not a fan of hardcording in the init script but investigating the issue I haven't found a more suitable way to solve it for our use case. Maybe another solution would be to add a modlua footer exporting this variable in the affected modules?
Currently we ship curl in the compat layer, so there's no way to avoid setting this in the initialisation script. If it ever came to be that we stopped doing that, then it would be enough to set this via an Lmod hook (this may be worth a comment in the init script where this is done)
The reason will be displayed to describe this comment to others. Learn more.
Looks good but can you add a comment to mention that if curl we're removed from the compat layer we could do this via the cURL module file (or an Lmod hook) instead
I'm not completely sure anymore if this can now be done with the bot (we did make some changes related to including the init scripts). Let's try it, and otherwise I can do it manually.
New job on instance eessi-bot-mc-aws for architecture x86_64-generic for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.07/pr_623/14519
date
job status
comment
Jul 16 07:50:03 UTC 2024
submitted
job id 14519 awaits release by job manager
Jul 16 07:50:26 UTC 2024
released
job awaits launch by Slurm scheduler
Jul 16 11:44:04 UTC 2024
running
job 14519 is running
Jul 16 11:56:25 UTC 2024
finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-14519.out ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.gz created!
Artefacts
eessi-2023.06-software-linux-x86_64-generic-1721130246.tar.gzsize: 0 MiB (2121 bytes) entries: 1 modules under 2023.06/software/linux/x86_64/generic/modules/all
no module files in tarball
software under 2023.06/software/linux/x86_64/generic/software
no software packages in tarball
other under 2023.06/software/linux/x86_64/generic
2023.06/init/eessi_environment_variables
Jul 16 11:56:25 UTC 2024
test result
😁 SUCCESS (click triangle for details)
ReFrame Summary
[ PASSED ] Ran 14/14 test case(s) from 14 check(s) (0 failure(s), 0 skipped, 0 aborted)
Details
✅ job output file slurm-14519.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Jul 16 12:01:55 UTC 2024
uploaded
transfer of eessi-2023.06-software-linux-x86_64-generic-1721130246.tar.gz to S3 bucket succeeded
2023.06-software.eessi.io2023.06 version of software.eessi.iobot:deployAsk bot to deploy missing software installations to EESSIbugSomething isn't working
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bedroge
added
bug
As reported in the EESSI support portal issue #25, curl fails in RHEL 8 and above systems as CA files location differs. Works for all rhel based systems as I could reproduce the issue also in them.
I am not a fan of hardcording in the init script but investigating the issue I haven't found a more suitable way to solve it for our use case. Maybe another solution would be to add a modlua footer exporting this variable in the affected modules?