| *** etienne has joined #ara | 02:23 | |
| *** etienne has quit IRC | 05:19 | |
| *** evrardjp has quit IRC | 05:33 | |
| *** evrardjp has joined #ara | 05:33 | |
| *** TKersten has joined #ara | 06:29 | |
| *** etienne has joined #ara | 14:29 | |
| *** TKersten has left #ara | 15:41 | |
| -openstackstatus- NOTICE: The Gerrit service on review.opendev.org is being restarted quickly to troubleshoot an SMTP queuing backlog, downtime should be less than 5 minutes | 16:40 | |
| *** etienne has quit IRC | 18:58 | |
| *** etienne has joined #ara | 19:44 | |
| *** msaladna has joined #ara | 23:37 | |
| msaladna | Hey guys, have a question on resuming a playbook by ID. During execution the system may reboot, which is then resumed with a systemd service. I tried passing playbook_id=n as an extra var to resume recording to that suspended playbook, but looks to be held internally in ara_default.py - https://github.com/ansible-community/ara/blob/master/ara/plugins/callback/ara_default.py#L268 | 23:41 |
|---|---|---|
| dmsimard | msaladna: o/ | 23:45 |
| dmsimard | there is no implementation in the callback to resume a playbook currently but I guess it is supported by the API | 23:46 |
| dmsimard | the ansible controller node reboots in the middle of the playbook execution ? | 23:47 |
| dmsimard | the ansible-playbook process would die as a result of the playbook so another ansible-playbook execution is another playbook | 23:50 |
| msaladna | Well it's an abrupt reboot and for example, https://api.ara.apiscp.com/playbooks/4.html?changed=True#results is the one that reboots, still in an in-progress or interrupted state | 23:53 |
| msaladna | https://api.ara.apiscp.com/playbooks/5.html?changed=True#results is the continuation | 23:53 |
| msaladna | I'm looking for a way to resume playbook #4 without creating #5 | 23:55 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!