On 9/20/23 5:24 AM, Ashok Reddy wrote:
I tried without using serial=1 but can’t make it to work

On Wed, 20 Sep 2023 at 5:06 PM, Ashok Reddy <ashokrd...@gmail.com> wrote:

    Hi David,

    I tried using block level but it throws error

Neither of these responses is informative.
What results - from the job log - constitute "can't make it work"? What exactly did you try? What did you change, and what did you change it to? When you tell us that "it throws error" without including - from the job log - the error that it throws, what possible response can you expect besides "Does it now? And what error did it throw exactly?"

We have established from many days ago that something is causing the equivalent of ignore_errors: true. We saw this in the job log. This may be related to something in your Ansible configuration. The output from the command

*ansible-config dump --only-changed*

would tell us, but you still have not shared that with us. *Please post the output from that command.*


It could also be related to how your task file is being invoked from your playbook: import, include, indirectly through roles:, or some other way. *Could you please tell us how this task file gets pulled into the play?*


Another thing: *What does your **ansible-playbook**command line look like?* Knowing the parameters you are using might be very helpful in our trying to reproduce the issue you are having.


*What does the top of your playbook look like?* I mean the section before any tasks:, pretasks:, roles:, handlers:, etc. There are keywords and values there that directly affect how plays run.

We're trying to help you. That would be much easier to do if you provided the requested information.
--
Todd

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/700e6e27-6cf0-cd1f-fd64-7eeeb67bce64%40gmail.com.

Reply via email to