Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SlurmDBD config does not work #6

Open
natefoo opened this issue Mar 6, 2020 · 5 comments · Fixed by roumano/ansible-slurm#1 · May be fixed by #8 or #12
Open

SlurmDBD config does not work #6

natefoo opened this issue Mar 6, 2020 · 5 comments · Fixed by roumano/ansible-slurm#1 · May be fixed by #8 or #12

Comments

@natefoo
Copy link
Member

natefoo commented Mar 6, 2020

The config template, generic.conf.j2 expects to be run in a loop over a list of dicts, but the task that templates it does not do so.
@torfinnnome torfinnnome linked a pull request May 22, 2020 that will close this issue
Open
@torfinnnome
Copy link

Oh, after submitting this pull request, I noticed that this is already fixed in #1. However, we also need #5.

@bdeetz
Copy link

bdeetz commented Jan 27, 2021

Also experiencing this issue on v0.1.3

TASK [galaxyproject.slurm : Install slurmdbd.conf] **************************************************************************************************************************************
fatal: [REDACTED]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'item' is undefined"}

roumano pushed a commit to roumano/ansible-slurm that referenced this issue Mar 8, 2021
Fix galaxyproject#6
5ef8e79 
- on tasks `Install slurmdbd.conf` , fix AnsibleUndefinedVariable: 
'item' is undefined"
- Create directory path of PIDfile
- Modify the systemd service with PIDfile
- Add Handler to reload systemd

Still a bug exist on a refresh install `Ensure slurmdbd is enabled and 
running` will failed as it's running before systemd daemon-reload
This was referenced Mar 8, 2021
Open
Merged
@ianhinder
Copy link

I just ran into this issue when I installed the role for the first time and tried out the example playbook. Is there a plan for getting it fixed? I’m a bit confused from the discussion above whether it is thought to be fixed, or is still acknowledged as a problem in the default install.

@michaelniemand
Copy link

I just ran into this issue when I installed the role for the first time and tried out the example playbook. Is there a plan for getting it fixed? I’m a bit confused from the discussion above whether it is thought to be fixed, or is still acknowledged as a problem in the default install.

When you use the master branch instead of the tag, the error is fixed. You can also check out the merged link above the see the exact fixes

@natefoo
Copy link
Member Author

natefoo commented Nov 17, 2021

The fix should be included in the tagged version 1.0.0 as well, which is upload to Ansible Galaxy.

@cmeesters cmeesters mentioned this issue Oct 26, 2022
Closed
cmeesters added a commit to snakemake/snakemake that referenced this issue Oct 26, 2022
@cmeesters
according to galaxyproject/ansible-slurm#6 a fix has been introduced …
0dd736d 
…to the galaxy ansible slurm runner - this is an attempt to try the fix, as there is no release, yet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
5 participants
@ianhinder @natefoo @torfinnnome @bdeetz @michaelniemand