Running yum updates with ansible

[Chris Bidwell - NOAA Federal]

Hey all, 

So I've done a lot of yum updates with ansible and several times I get issues where partial updates are run and it says it's been completed, however, I reboot and I'm in a kernel panic because the new kernel didn't update properly so I have to revert to the previous kernel and remove the newest and reinstall it again.  I also often wind up with transactions that haven't been completed.    Has anyone experienced this before?

Thanks!

Chris

[Jonathan Lozada De La Matta]

what version of ansible are you using? 

--
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 post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAHKi8CgQ87cs0toXZ4pqefZjoA_Yv0mc89DcMLYih7j6nVHgew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Jonathan lozada de la matta

AUTOMATION PRACTICE

 

[Chris Bidwell]

Using the latest of 2.7.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[S C Rigler]

I've seen this also. When the new kernel installs there is a post
transaction scriplet to build the initrd. In some cases it doesn't
build correctly (I see it fail maybe 1-5% of the time) and you'll get
a panic when the system reboots. I don't know that I've seen enough
to blame it on Ansible, though.

--Steve

[Jonathan Lozada De La Matta]

I had a similar issue before with centos but, it was more like a limit ( for example 4 ) of kernels that could be install at the moment but, the current running kernel was uninstalled and the new one did not install correctly so the system hanged during booting.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAFbiokfshO7ytXf3RxojLac34PvgMTA%3DDdz3M_igQ7zLakFJxA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Chris Bidwell - NOAA Federal]

So does anyone have any recommendations on how to alleviate this problem?  Perhaps some sort of delay before exiting or something?

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAFYJA%2BJkQ-rEp86OHruqn40Tfi-C3jSkbEjkiHJzK7c-ACmt1w%40mail.gmail.com.

[Jonathan Lozada De La Matta]

well like mentioned this is not ansible specific so i suggest you research more into the OS side.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAHKi8Cipf75nDoKznxkO%2Bz1stTMZMDOPSk%3DdsP6XaN9niH7wtQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Chris Bidwell - NOAA Federal]

Well if I run it manually, I don't have any issues.  I'll look into it further.  Thanks again.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAFYJA%2BLfY7Pp9FX4YJd9ZsZTu3WuPDFWy6S-bTL7GPiCf%2BgnSg%40mail.gmail.com.

[boncalo mihai]

I know this is an ansible group but you could attach dmesg output if you get one after the kernel fails to boot. Check    /var/log/boot-(date) /var/log/dmesg /var/log/yum.log ...you can start from there.

Also I don't know if you're logging ansible actions every time, but you could find answers there.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAHKi8CjhDgXr00NuOkbd2f4VGbZRb_PtaR6Pqv20VzAw6CX-5A%40mail.gmail.com.