Summary: | Cannot delete account after recent migration to 20.11.8 from 20.02 | ||
---|---|---|---|
Product: | Slurm | Reporter: | Dane Kennedy <dane> |
Component: | Database | Assignee: | Jacob Jenson <jacob> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | 6 - No support contract | ||
Priority: | --- | CC: | bas.vandervlies, kilian, stephan.roth |
Version: | 20.11.8 | ||
Hardware: | Linux | ||
OS: | Linux | ||
Site: | -Other- | Alineos Sites: | --- |
Atos/Eviden Sites: | --- | Confidential Site: | --- |
Coreweave sites: | --- | Cray Sites: | --- |
DS9 clusters: | --- | HPCnow Sites: | --- |
HPE Sites: | --- | IBM Sites: | --- |
NOAA SIte: | --- | NoveTech Sites: | --- |
Nvidia HWinf-CS Sites: | --- | OCF Sites: | --- |
Recursion Pharma Sites: | --- | SFW Sites: | --- |
SNIC sites: | --- | Linux Distro: | --- |
Machine Name: | CLE Version: | ||
Version Fixed: | Target Release: | --- | |
DevPrio: | --- | Emory-Cloud Sites: | --- |
Description
Dane Kennedy
2021-09-28 04:17:33 MDT
Dane, I am sorry you have encountered this issue. The SchedMD support team can help you resolve this issue, but first your site will need to purchase a support contact. Is IDIA open to purchasing support? Thank you, Jacob Hi Jacob, Thank you very much, unfortunately we're a relatively small academic organisation and I don't think we can afford a support contract. Fortunately I managed to check your open source code and found various columns that needed a default empty string set on those columns, so I manually updated those and everything is functional again now. Thank you for a wonderful product, Dane. On Tue, Sep 28, 2021 at 6:39 PM <bugs@schedmd.com> wrote: > *Comment # 1 <https://bugs.schedmd.com/show_bug.cgi?id=12558#c1> on bug > 12558 <https://bugs.schedmd.com/show_bug.cgi?id=12558> from Jacob Jenson > <jacob@schedmd.com> * > > Dane, > > I am sorry you have encountered this issue. The SchedMD support team can help > you resolve this issue, but first your site will need to purchase a support > contact. Is IDIA open to purchasing support? > > Thank you, > Jacob > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > > MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER max_tres_pj SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER max_tres_pn SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER max_tres_mins_pj SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER max_tres_run_mins SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER grp_tres SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER grp_tres_mins SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER grp_tres_run_mins SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER qos SET DEFAULT ''; MariaDB [slurm_acct_db]> ALTER TABLE `CLUSTER_NAME_assoc_table` ALTER delta_qos SET DEFAULT ''; ← the fix :-). I ran into the same problem, but circumvented it by allowing NULL for the afflicted columns: ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `max_tres_pj` `max_tres_pj` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `max_tres_pn` `max_tres_pn` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `max_tres_mins_pj` `max_tres_mins_pj` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `max_tres_run_mins` `max_tres_run_mins` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `grp_tres` `grp_tres` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `grp_tres_mins` `grp_tres_mins` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `grp_tres_run_mins` `grp_tres_run_mins` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `qos` `qos` BLOB NULL; ALTER TABLE `<CLUSTER_NAME>_assoc_table` CHANGE `delta_qos` `delta_qos` BLOB NULL; My reason for this fix is, according to https://dev.mysql.com/doc/refman/5.7/en/data-type-defaults.html "The BLOB, TEXT, GEOMETRY, and JSON data types cannot be assigned a default value." So im my opinion the query generated when deleting a user: update "<CLUSTER_NAME>_assoc_table" as t1 set mod_time=1634639485, deleted=1, def_qos_id=DEFAULT, shares=DEFAULT, max_jobs=DEFAULT, max_jobs_accrue=DEFAULT, min_prio_thresh=DEFAULT, max_submit_jobs=DEFAULT, max_wall_pj=DEFAULT, max_tres_pj=DEFAULT, max_tres_pn=DEFAULT, max_tres_mins_pj=DEFAULT, max_tres_run_mins=DEFAULT, grp_jobs=DEFAULT, grp_submit_jobs=DEFAULT, grp_jobs_accrue=DEFAULT, grp_wall=DEFAULT, grp_tres=DEFAULT, grp_tres_mins=DEFAULT, grp_tres_run_mins=DEFAULT, qos=DEFAULT, delta_qos=DEFAULT, priority=DEFAULT where (id_assoc=<ASSOC_ID>); is incorrect in trying to set DEFAULT values for the TEXT and BLOB columns for this version of MySQL. Ignore what I called a "fix" above. slurmdbd crashes with these changes when adding/removing users from Slurm accounts with sacctmgr We have this issue as well. Is there a fix? we have a support contract Just for the reference the right solution was also in this ticket and also mentioned here: * https://bugs.schedmd.com/show_bug.cgi?id=1294 (In reply to Bas van der Vlies from comment #7) > Just for the reference the right solution was also in this ticket and also > mentioned here: > * https://bugs.schedmd.com/show_bug.cgi?id=1294 For future reference, if anyone's looking at this, I believe the actual bug referencing that issue is https://bugs.schedmd.com/show_bug.cgi?id=12947 Cheers, -- Kilian |