Ticket 8934

Summary: Fix configless SLURM to deploy correct file for plugstack.conf
Product: Slurm Reporter: Trey Dockendorf <tdockendorf>
Component: ConfigurationAssignee: Tim Wickberg <tim>
Status: RESOLVED DUPLICATE QA Contact:
Severity: C - Contributions    
Priority: ---    
Version: 20.02.1   
Hardware: Linux   
OS: Linux   
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: ---

Description Trey Dockendorf 2020-04-23 19:39:17 MDT
It looks like plugstack.conf is deploying topology.conf when using configless.

This is for Ohio Supercomputer Center, we don't yet have a support contract but it's in the works I believe.

Might be related to #8603.  This is the patch to fix the issue:

--- a/src/common/fetch_config.c
+++ b/src/common/fetch_config.c
@@ -347,7 +347,7 @@ extern int write_configs_to_conf_cache(config_response_msg_t *msg,
                return SLURM_ERROR;
        if (_write_conf(dir, "knl_generic.conf", msg->knl_generic_config))
                return SLURM_ERROR;
-       if (_write_conf(dir, "plugstack.conf", msg->topology_config))
+       if (_write_conf(dir, "plugstack.conf", msg->plugstack_config))
                return SLURM_ERROR;
        if (_write_conf(dir, "topology.conf", msg->topology_config))
                return SLURM_ERROR;
Comment 1 Tim Wickberg 2020-04-24 11:42:37 MDT
Thanks for the report, Trey.

We have a patch waiting to go in alongside a few other fixes for the configless mode of operation, and this was previously reported by Matt Mix on bug 8603 which I'm closing this as a duplicate of. This, alongside a few other fixes accumulating on an internal ticket should all be in 20.02.2 when released.

- Tim

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