| Summary: | Upgrade Question | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Lyn <schedulerqueen> |
| Component: | slurmctld | Assignee: | David Bigagli <david> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 3 - Medium Impact | ||
| Priority: | --- | CC: | brian, da |
| Version: | 14.03.10 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | NASA - NCCS | Alineos Sites: | --- |
| Atos/Eviden Sites: | --- | Confidential Site: | --- |
| Coreweave sites: | --- | Cray Sites: | --- |
| DS9 clusters: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | --- | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Linux Distro: | --- |
| Machine Name: | CLE Version: | ||
| Version Fixed: | Target Release: | --- | |
| DevPrio: | --- | Emory-Cloud Sites: | --- |
|
Description
Lyn
2014-12-01 10:26:58 MST
We'll probably tag 14.03.11 later in December. There is no problem mixing and matching hardware, OS, even 32- and 64-bit systems in the same Slurm cluster. You may well need different Slurm builds for the different distros. On a related note, we discovered today that Slurm Perl APIs built with Perl version 5.20 will not run on a system having Perl version 5.18 (and vice versa). We have never observed this problem in the past, so this problem might be specific to certain versions of Perl. In any case, a Perl update may necessitate that Slurm's Perl APIs and our torque command wrappers be rebuilt. Hy Lynn, did this answer your question? David Hi David, Yes, Moe's confirmation gave us the warm-n-fuzzy feeling we needed. :) Please feel free to close this ticket. Thanks and Best, Lyn On Tue, Dec 2, 2014 at 11:40 AM, <bugs@schedmd.com> wrote: > *Comment # 2 <http://bugs.schedmd.com/show_bug.cgi?id=1288#c2> on bug > 1288 <http://bugs.schedmd.com/show_bug.cgi?id=1288> from David Bigagli > <david@schedmd.com> * > > Hy Lynn, did this answer your question? > > David > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > > Information provided. David |