| Summary: | is the client version forward compatible? | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Vito Burggraf <vito.burggraf> |
| Component: | Configuration | Assignee: | Marcin Stolarek <cinek> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 4 - Minor Issue | ||
| Priority: | --- | CC: | cinek |
| Version: | 20.02.2 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | SiFive | 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
Vito Burggraf
2021-07-13 00:24:52 MDT
Vito, This won't work. Slurm client commands don't negotiate protocol version with slurmctld and other daemons, they just send messages using the protocol version they belong to. Slurmctld supports two older versions, so older commands work with newer slurmctld, but by its nature, those can't support a protocol that wasn't available at its release time. Using a newer user command with older slurmctld will result in errors like: >slurmctld: error: slurm_unpack_received_msg: Invalid Protocol Version XXXX from uid=... at ....:.... On client side it will show: >error: Unable to allocate resources: Zero Bytes were transmitted or received cheers, Marcin Vito, Is there anything else I can help you with here? cheers, Marcin I'll go ahead and mark the case as closed now. Should you have any questions please reopen. cheers, Marcin |