Ticket 6387 - sinfo -N prints multiple lines
Summary: sinfo -N prints multiple lines
Status: RESOLVED FIXED
Alias: None
Product: Slurm
Classification: Unclassified
Component: User Commands (show other tickets)
Version: 17.11.12
Hardware: Linux Linux
: 4 - Minor Issue
Assignee: Albert Gil
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2019-01-21 03:25 MST by Ole.H.Nielsen@fysik.dtu.dk
Modified: 2019-03-05 12:32 MST (History)
0 users

See Also:
Site: DTU Physics
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: 18.08.6
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
Description Ole.H.Nielsen@fysik.dtu.dk 2019-01-21 03:25:15 MST
The sinfo manual pages states:

-N, --Node
    Print information in a node-oriented format with one line per node. The default is to print information in a partition-oriented format. This is ignored if the --format option is specified. 

However, our nodes who are members of multiple partitions are printed with multiple lines per node in stead of the documented one line per node.  For example:

$ sinfo -N -n d001
NODELIST   NODES PARTITION STATE 
d001           1    xeon8* alloc 
d001           1  xeon8_48 alloc 

Request: Could you kindly update the sinfo manual page, or correct the sinfo command to behave as documented?

Thanks,
Ole
Comment 5 Albert Gil 2019-02-18 06:45:29 MST
Hi Ole,

You are right, the documentation is not well specified.
If a node is in several partitions one line per partition and node is shown.
Unless --partition is also specified, then only one line per node on the specified partition will be shown.

We are improving the documentation and release it soon.

Thanks for reporting it,
Albert
Comment 7 Albert Gil 2019-03-05 12:32:36 MST
Hi Ole,
I'm closing this bug as documentation has been improved in 12e8f2959212 and will be released soon as part of the 18.08-6.

Thanks for reporting it,
Albert