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.

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

skip wait_for in reboot handler ( for ansible-pull ) #4

Closed
martbhell opened this issue Jul 8, 2016 · 4 comments
Closed

skip wait_for in reboot handler ( for ansible-pull ) #4

martbhell opened this issue Jul 8, 2016 · 4 comments
Assignees

Comments

@martbhell
Copy link
Contributor

martbhell commented Jul 8, 2016

The handler to reboot has a "wait_for" - this needelessly makes this role pause for 300s before rebooting - also when ansible-pull is running. Can we skip that one somehow on ansible-pull runs?

For push mode then it's nice to keep this one as the play shouldn't fail - just reboot and then wait for the node to come back online.

https://github.com/CSC-IT-Center-for-Science/ansible-role-cuda/blob/master/handlers/main.yml

@martbhell
Copy link
Contributor Author

As far as I can see there's no special variable in ansible_facts one could use to figure out if we are running ansible-pull. So instead we set a variable when running ansible-pull.

Conditional updated for the wait_for handler in e1af63b

@martbhell martbhell self-assigned this Jul 19, 2016
@martbhell
Copy link
Contributor Author

Testing the change on our GPU node

@martbhell
Copy link
Contributor Author

Not perfect. It didn't restart at all now after the cuda role on a new install.
Maybe one needs to remove the async/poll settings in the handler.

@martbhell
Copy link
Contributor Author

The wait_for does not apply anymore. Also added a handler 1 and task 2 which runs cuda_init.sh in ansible too (not only from rc.local). But after the file has changed or if /dev/nvidia0 does not exist. Idea here is to have a /dev/nvidia0 available on the GPU nodes before we start slurm (which fails if those files in gres.conf does not exist).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants