https://bugzilla.redhat.com/show_bug.cgi?id=1389791
M. Scherer <msche...@redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |msche...@redhat.com Resolution|--- |CURRENTRELEASE Last Closed| |2016-11-04 05:01:45 --- Comment #3 from M. Scherer <msche...@redhat.com> --- So the issue was that we did some change on apache (like various refactoring of the configuration file). This got applied in production and this should have resulted into a apache restart. However, due to https://github.com/ansible/ansible-modules-core/pull/4777 and due to use using a specific transport, the playbook were silently failing at the step "restart httpd", who then , for a unknow reason, was in some weird state. Short term solution: Restart apache. Mid term: we have to wait for ansible 2.2, which got released this week, and/or a backport of the bug fix. Both should happen soon (and automatically), so I suspect Long term, we need to : - lack of reporting on ansible side (which is on my todolist) - lack of monitoring (also on todo list) Both would have permitted a faster turn around. Also, managing to not schedule conferences for me while Nigel is out on PTO would be better, but I can't ask to the organiser, nor I can ask to India to change their dates. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=PCKYQw2KCd&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra