Re: [ansible-project] Is it possible to jump to the next task without waiting for any Reason Code / Output?

yeah ansible contains some prevention for bad init scripts where it will daemonize around them to "trick" them into returning. It's occasionally not perfect. I'm not familiar with Adobe CQ, but what OS are you managing when this happens? On Wed, Aug 6, 2014 at 2:02 PM, Karl E. Jorgensen wrote:

Re: [ansible-project] Is it possible to jump to the next task without waiting for any Reason Code / Output?

Hi On Wed, Aug 06, 2014 at 03:00:59AM -0700, Julián Jamardo wrote: > Hi everybody, > > I'm deploying Adobe CQ projects with Ansible, everything works fine except the > restart at the end of the deployment. > > The excerpt of the my playbook: > > - name: Stop of CQ instance > command: sudo

[ansible-project] Is it possible to jump to the next task without waiting for any Reason Code / Output?

Hi everybody, I'm deploying Adobe CQ projects with Ansible, everything works fine except the restart at the end of the deployment. The excerpt of the my playbook: - name: Stop of CQ instance command: sudo /etc/init.d/cq stop - name: make sure CQ is stopped service: name=cq stat