Ticket 9176 - sprio not showing any output
Summary: sprio not showing any output
Status: RESOLVED DUPLICATE of ticket 9177
Alias: None
Product: Slurm
Classification: Unclassified
Component: User Commands (show other tickets)
Version: 20.02.1
Hardware: Linux Linux
: 2 - High Impact
Assignee: Dominik Bartkiewicz
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2020-06-04 23:48 MDT by dl_support-hpc
Modified: 2020-06-05 01:01 MDT (History)
1 user (show)

See Also:
Site: WEHI
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 dl_support-hpc 2020-06-04 23:48:48 MDT 
Hi Support

I am running version 20.02.3 on slurmctld and slurmdbd on compute nodes 20.02.1

I have multifactor configured

PriorityType=priority/multifactor

When running sprio no output is shown, neither for individual job

[root@milton-sml-002 ~]# squeue 
             JOBID PARTITION     NAME     USER ST       TIME  NODES NODELIST(REASON) 
             36164   regular bionix-o   bedo.j  R      22:46      1 milton-med-004 

[root@milton-sml-002 ~]# sprio -j 36164
Unable to find jobs matching user/id(s) specified

[root@milton-sml-002 ~]# sprio -w
          JOBID PARTITION   PRIORITY       SITE        AGE  FAIRSHARE    JOBSIZE  PARTITION        QOS
        Weights                               1       8000      10000       3000          1       8000

This is very similar to bug 8727.

Thanks and Regards,
Laszlo
Comment 1 Dominik Bartkiewicz 2020-06-05 01:01:43 MDT 
Closing as a duplicate of bug 9177

*** This ticket has been marked as a duplicate of ticket 9177 ***