Ticket 4208 - host_file parsing rewards verbose users
Summary: host_file parsing rewards verbose users
Status: RESOLVED DUPLICATE of ticket 4169
Alias: None
Product: Slurm
Classification: Unclassified
Component: User Commands (show other tickets)
Version: 17.02.7
Hardware: Cray XC Linux
: 4 - Minor Issue
Assignee: Director of Support
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2017-10-02 11:07 MDT by Doug Jacobsen
Modified: 2017-10-02 13:05 MDT (History)
2 users (show)

See Also:
Site: NERSC
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 Doug Jacobsen 2017-10-02 11:07:20 MDT 
Hello,

<meta>This bug is the lowest possible sev4 available</meta>

We have a user that wants to enumerate many KNL nodes using syntax like:
nid01234*16
nid01235*16

and so on.

The user gets this _exact_ error string:

srun: error: Hostlist is too long for the allocate RPC!

Reviewing api/allocate.c slurm_read_hostfile(), this appears to be because it allocates a buffer 1024 bytes longer than the length of the file.  This essentially make the more compact syntax unworkable for larger allocations.

We reviewed bug 4169 in preparing this bug =)

Thanks,
Doug
Comment 1 Marshall Garey 2017-10-02 13:05:16 MDT 
Hi Doug,

I'm working on bug 4169 right now, and my fix should also fix this bug. Keep tabs on bug 4169. I'll mark this one as a duplicate of 4169 (I realize it's not the exact same problem, but the patch will fix both problems).

Marshall

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