Cluster configuration SLURM-DRMAA jammy release file missing.

, ,
1

Hi, I tried installing SLURM on my Ubuntu 22.04 server by following the tutorial from the Galaxy Training platform (Connecting Galaxy to a compute cluster) and ran into the following error during the installation:

fatal: [192.168.123.108]: FAILED! => changed=false
msg: ‘Failed to update apt cache: E:The repository ‘‘Index of /natefoo/slurm-drmaa/ubuntu jammy Release’’ does not have a Release file., W:Updating from such a repository can’‘t be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:https://repos.influxdata.com/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details., W:https://packages.grafana.com/oss/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.’

I was wondering if SLURM will be getting a release file for jammy and if so, if this is already under development. If not, are there any alternatives supported by Galaxy which could be used in a production environment?
Thanks in advance!

2

Hi @hexylena, sorry for bothering you, but would you by any chance happen to know any alternatives, since I doubt any new releases for compatibility with Ubuntu 22.04 are going to be released soon. Otherwise, I will just keep running the jobs one by one without connecting to a cluster and use local runners for now. Thanks in advance!

3

Hi! Yes, apologies. I’m filing the issue here: slurm-drmaa for Ubuntu Jammy · Issue #73 · natefoo/slurm-drmaa · GitHub
Alternatives:

  1. Compile slurm-drmaa yourself (quite some work)
  2. Use a different DRM (maybe less work but, completely different things to learn and there’s no nice tutorial for it.)

The code for slurm-drmaa is all here, you might just be able to ./configure && make (assuming you have the dependencies) but it’s probably non-trivial.

1 Like
4

Sorry for the wait! A 22.04/jammy deb is now available in the PPA. Please give it a try and let me know if there are issues.

1 Like
5

Sorry for the late reply and thank you for the update! I tried installing it and got the following error:

fatal: [xxx.xxx.xxx.xxx]: FAILED! => changed=false
msg: ‘Failed to update apt cache: W:Nate Coraor in Launchpad aa/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/e tc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details., W:h ttps://repos.influxdata.com/ubuntu/dists/jammy/InRelease: Key is stored in legac y trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt -key(8) for details., W:https://packages.grafana.com/oss/deb/dists/stable/InRele ase: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details., E:Repository ‘‘https://packages .grafana.com/oss/deb stable InRelease’’ changed its ‘‘Origin’’ value from ‘‘graf ana stable’’ to ‘’. stable’‘, E:Repository ‘‘https://packages.grafana.com/oss/de b stable InRelease’’ changed its ‘‘Label’’ value from ‘‘grafana stable’’ to ‘’. stable’‘’

The error is caused by the deprecation of the APT key management utility, which I think is part of the Ubuntu 22.04 update. Would it be possible to add/change the variable in order to get rid of the error, or is it up to the user to move the apt-key?
Thanks in advance!

More about the APT-key deprecation:

APT-KEY(8)

NAME
apt-key - Deprecated APT key management utility
…
DEPRECATION
Except for using apt-key del in maintainer scripts, the use of apt-key is deprecated. This section shows how to replace existing use of apt-key.

   If your existing use of apt-key add looks like this:

   wget -qO- https://myrepo.example/myrepo.asc | sudo apt-key add -

   Then you can directly replace this with (though note the recommendation below):

   wget -qO- https://myrepo.example/myrepo.asc | sudo tee /etc/apt/trusted.gpg.d/myrepo.asc

   Make sure to use the "asc" extension for ASCII armored keys and the "gpg" extension for the binary OpenPGP format (also known as "GPG key public ring"). The
   binary OpenPGP format works for all apt versions, while the ASCII armored format works for apt version >= 1.4.

   Recommended: Instead of placing keys into the /etc/apt/trusted.gpg.d directory, you can place them anywhere on your filesystem by using the Signed-By option in
   your sources.list and pointing to the filename of the key. See sources.list(5) for details. Since APT 2.4, /etc/apt/keyrings is provided as the recommended
   location for keys not managed by packages. When using a deb822-style sources.list, and with apt version >= 2.4, the Signed-By option can also be used to include
   the full ASCII armored keyring directly in the sources.list without an additional file.
6

Edit: I got rid of the error using the following command:

sudo apt-key export 12788738 | sudo gpg --dearmour -o /etc/apt/trusted.gpg.d/slurm.gpg

But immediatly ran into a new error:

fatal: [192.168.123.108]: FAILED! => changed=false
  checksum: 7d99e1e5d268baa1c56acfee8616bdf4d4525ab4
  msg: Destination directory /etc/slurm-llnl does not exist

Any ideas on how to fix this error?

7

This should be fixed as of version 1.0.2 of the galaxyproject.slurm role.

1 Like