Slurm specific settings breaking uploads on k8s instance

[pcm32]

Hi there!

Recently we revamped one of our k8s instances and on a new download of the tool.yml file we are getting now an error on data uploads related to the slurm entries in the tools.yml:

galaxy.jobs.mapper ERROR 2025-02-14 14:17:24,036 [pN:job_handler_0,p:8,tN:JobHandlerQueue.monitor_thread] Caught unhandled exception while attempting to cache job destination:
Traceback (most recent call last):
  File "/galaxy/server/lib/galaxy/jobs/mapper.py", line 236, in __cache_job_destination
    self.cached_job_destination = self.__determine_job_destination(
  File "/galaxy/server/lib/galaxy/jobs/mapper.py", line 224, in __determine_job_destination
    job_destination = self.__handle_dynamic_job_destination(raw_job_destination)
  File "/galaxy/server/lib/galaxy/jobs/mapper.py", line 204, in __handle_dynamic_job_destination
    return self.__handle_rule(expand_function, destination)
  File "/galaxy/server/lib/galaxy/jobs/mapper.py", line 207, in __handle_rule
    job_destination = self.__invoke_expand_function(rule_function, destination)
  File "/galaxy/server/lib/galaxy/jobs/mapper.py", line 124, in __invoke_expand_function
    return expand_function(**actual_args)
  File "/galaxy/server/.venv/lib/python3.10/site-packages/tpv/rules/gateway.py", line 50, in map_tool_to_destination
    return ACTIVE_DESTINATION_MAPPER.map_to_destination(app, tool, user, job)
  File "/galaxy/server/.venv/lib/python3.10/site-packages/tpv/core/mapper.py", line 157, in map_to_destination
    gxy_destination = app.job_config.get_destination(d.id)
  File "/galaxy/server/lib/galaxy/jobs/__init__.py", line 797, in get_destination
    return copy.deepcopy(self._get_single_item(self.destinations[id_or_tag]))
KeyError: 'tpvdb_slurm'

Should those tpvdb_slurm specific defaults should be there? maybe they could sit on a slurm specific file?

Thanks!

[nuwang]

the slurm entry is marked abstract and therefore, should not have any effect. It's weird that it's trying to route a job to an abstract destination - that shouldn't really happen. Can you let us know what your TPV version is and maybe also show any relevant TPV config files?