Ticket 24215 - Empty associations fields in v0.0.4{3,4}_assoc_short
Summary: Empty associations fields in v0.0.4{3,4}_assoc_short
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: slurmrestd (show other tickets)
Version: 25.05.4
Hardware: Linux Linux
: 6 - No support contract
Assignee: Jacob Jenson
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2025-11-27 06:23 MST by Rémi Palancher
Modified: 2025-11-27 06:23 MST (History)
0 users

See Also:
Site: -Other-
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Rémi Palancher 2025-11-27 06:23:34 MST 
Hello SchedMD,

The account and user properties are empty in association object of slurmdb job endpoint starting with Slurm REST API v0.0.43:

root@admin:~# curl -s --header X-SLURM-USER-TOKEN:$SLURM_JWT http://localhost:6820/slurmdb/v0.0.40/job/15 | jq .jobs[].association
{
  "account": "optic",
  "cluster": "hpc",
  "partition": "",
  "user": "jstrong",
  "id": 17
}
root@admin:~# curl -s --header X-SLURM-USER-TOKEN:$SLURM_JWT http://localhost:6820/slurmdb/v0.0.41/job/15 | jq .jobs[].association
{
  "account": "optic",
  "cluster": "hpc",
  "partition": "",
  "user": "jstrong",
  "id": 17
}
root@admin:~# curl -s --header X-SLURM-USER-TOKEN:$SLURM_JWT http://localhost:6820/slurmdb/v0.0.42/job/15 | jq .jobs[].association
{
  "account": "optic",
  "cluster": "hpc",
  "partition": "",
  "user": "jstrong",
  "id": 17
}
root@admin:~# curl -s --header X-SLURM-USER-TOKEN:$SLURM_JWT http://localhost:6820/slurmdb/v0.0.43/job/15 | jq .jobs[].association
{
  "account": "",
  "cluster": "hpc",
  "partition": "",
  "user": "",
  "id": 17
}

Current version:

root@admin:~# slurmrestd -V
slurm 25.05.4

I get the same behavior with REST API v0.0.43 and v0.0.44 on Slurm 25.11.0.

Is this a regression?