looking for support

23 views
Skip to first unread message

Shyju Krishnan

unread,
Jul 24, 2022, 9:57:13 AM7/24/22
to ansible...@googlegroups.com
image.png

Antony Stone

unread,
Jul 24, 2022, 10:19:45 AM7/24/22
to ansible...@googlegroups.com
On Sunday 24 July 2022 at 15:56:46, Shyju Krishnan wrote:

> [image: image.png]

Please:

1. Copy and paste text, don't post screenshots (especially in difficult-to-read
colour combinations)

2. Show us the command you ran before getting the error

3. Show us the text of the error in as readable a format as possible

4. Show us your playbook (if it's small) or the relevent section of it (if
it's big)

5. Consider using pastebin or similar if you want to show us more than arounnd
25 lines of playbook.


Thanks,


Antony.

--
Schrödinger's rule of data integrity: the condition of any backup is unknown
until a restore is attempted.

Please reply to the list;
please *don't* CC me.

Abhijeet Kasurde

unread,
Jul 25, 2022, 1:54:42 AM7/25/22
to ansible...@googlegroups.com
I totally agree with Antony. It will be easier to answer the question if you provide these details.

Regarding your question, the task mentioned before the 'Cordon and Drain Node' task failed with a non-zero return value and the failed ('Cordon and Drain Node') task in the screenshot is expecting zero return code with JSON output.
--
Thanks,
Abhijeet Kasurde

Shyju Krishnan

unread,
Jul 25, 2022, 3:27:24 AM7/25/22
to ansible...@googlegroups.com
Hi, 

Now it is working 
however the first time master node the corden and update the patch and rebooted after that only getting this error
i just rerun the playbook again now it is working 

i will let you know if any issues 

--
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-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAFwWkHqt0QBmeeNUrLRL%3D3cQq4_th-snDh3LxwStk%3DYt2ZskLg%40mail.gmail.com.

Dick Visser

unread,
Jul 25, 2022, 6:37:53 AM7/25/22
to ansible...@googlegroups.com
So we don't know what the problem was, and instead of receiving some context, we now also don't know what the solution was.
This one is ranked high in the top 10 of useless threads...

--
Sent from Gmail Mobile
Reply all
Reply to author
Forward
0 new messages