Too old glibc in rocky 9 osimag

[raskallen]

Hi

To be able to run interactive apps wich depends on XFCE, which doesn't work in RHEL 10 because missing xfce wayland support, I am trying to build a Rocky 9.3 osimage to run on my hosts. I am following the instructions in the PDF and comments in the ansible playbooks.

When I boot a node with this image, slurmd refuses to start with these errors. How do I approach this? Upgrading glibc is not possible, so I guess I will need to get an older version of ohpc.

[root@testnode ~]# systemctl status slurmd
× slurmd.service - Slurm node daemon
     Loaded: loaded (/usr/lib/systemd/system/slurmd.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Wed 2026-05-27 15:39:07 CEST; 16h ago
    Process: 2426 ExecStart=/usr/sbin/slurmd --systemd $SLURMD_OPTIONS (code=exited, status=1/FAILURE)
   Main PID: 2426 (code=exited, status=1/FAILURE)
        CPU: 2ms

May 27 15:39:07 testnode.int.nibio.no systemd[1]: Starting Slurm node daemon...
May 27 15:39:07 testnode.int.nibio.no slurmd[2426]: /usr/sbin/slurmd: /lib64/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /opt/ohpc/pub/libs/hwloc/lib/libhwloc.so.15)
May 27 15:39:07 testnode.int.nibio.no slurmd[2426]: /usr/sbin/slurmd: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /opt/ohpc/pub/libs/hwloc/lib/libhwloc.so.15)
May 27 15:39:07 testnode.int.nibio.no systemd[1]: slurmd.service: Main process exited, code=exited, status=1/FAILURE
May 27 15:39:07 testnode.int.nibio.no systemd[1]: slurmd.service: Failed with result 'exit-code'.
May 27 15:39:07 testnode.int.nibio.no systemd[1]: Failed to start Slurm node daemon.
[root@testnode ~]# 

my compute-rocky93.yml looks like this:

---
- hosts: localhost
  pre_tasks:
  #
  # the image name can be set in the below fact.
  #
  - name: Set image name
    set_fact:
      image_name: "rocky93-image"
    tags: always

- import_playbook: imports/trinity-redhat-image-create.yml
  vars:
    image_name: "{{ hostvars['localhost']['image_name'] }}"
    # The password to set up for the root user in the image.
    # If empty, it will be generated at random.
    #
    image_password:
    #
    # Alternative distribution build. Supported are Rocky + Centos, version 8, 9, 8.9, 9.3
    # or any docker image, e.g. rockylinux:8
    alternative_distribution: Rocky-9.3
    # 
    # The alternative source can be 'base' or 'docker'
    alternative_image_source: 'base'

- import_playbook: imports/trinity-redhat-image-setup.yml
  vars:
    hostlist: "{{ hostvars['localhost']['image_name'] }}.osimages.luna"

- hosts:
    - "{{ hostvars['localhost']['image_name'] }}.osimages.luna"
  roles:
    - role: trinity/slurm
      slurm_conf_path: '{{ trix_shared }}/etc/slurm'
      slurm_spool_path: '{{ trix_shared }}/var/spool/slurm'
      munge_conf_path: '{{ trix_shared }}/etc/munge'
      when: "'slurm' in workload_manager "
      tags: slurm

- hosts: controllers
  roles:
    - role: luna/osimage-pack
      vars:
         params:
            image_name: "{{ hostvars['localhost']['image_name'] }}"
      tags: pack-images

[aphmschonewille]

Hi Raskalen,

We are struggling with work arounds for the remote desktop/wayland issue as well. So far no good.

I'm happy you were able to build an el9 image and boot, but now you see the limitations of the ohpc stack. Hwloc for slurm is hard coded to look at the ohpc stack, which of course for el10 is not compliant with el9.

There is light at the tunnel, as we will introduce our own slurm builds that work cross platform, cross release.
I can give you a method if you like (needs a bit of copying files, editing some others) that allow you to remove the ohpc slurm stack and use ours. Technically, the first 'hints' are already in the development branch (publicly available)...
The second option is to wait till mid june for our new release for TrinityX (16)

-Antoine

[raskallen]

Actually I have gotten the remote desktop working with Gnome. But figuring out how to use Gnome for other apps like MATLAB and OSC QGIS seems to be a lot of work (and frustrations I guess). Good to hear that theres light in the tunnel.

I am very interested in this method you are mentioning. I don't my copying, editing, compiling or rewriting things. Been doing that since my first custom linux kernel compiliation back in 1993. :D

[aphmschonewille]

I feel your pain. I sometimes miss my good old kernel 0.9.something, but also 1.2.8. So simple, so elegant. 2.0 was already doing modules. Then 3..... alas. I get you.
Sometimes i am jealous with the dictated way dll-s are done. It lags flexibility but solved the inter version complexity.

Am happy hear that you got something going with gnome. We were investigating the latest ood 4.2 something, which introduced yet other dependency issues. With el10.2 coming out recently we took a step back on this. Wayland, to be continued. The inter dustri slurm issue is being tackled though.

-Antoine