How to make the package module useful again?

[Orion Poplawski]

We manage both Ubuntu and RedHat/Fedora systems from the same playbooks. One of the tools that has been very helpful for us in this is the generic "package" module. However, with the recent change to the yum lock timeout behavior with ansible 2.8, we are now required to set a long "lock_timeout" to avoid yum failing during the periodic (hourly) yum cache updates and other operations. This parameter breaks using package with apt:

Unsupported parameters for (apt) module: lock_timeout

So, any suggestions as to how to make the package module useful again?

- Orion

[Matt Martz]

To avoid duplicating my answer, and just for completeness.  Please see my response here: https://github.com/ansible/ansible/issues/57189#issuecomment-499165098

--
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/96c6ea54-92bf-4e98-ab64-69daebe7c2ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Matt Martz
@sivel
sivel.net

[Brian Coca]

"package" was always 'limited' in functionality, you just happened not
to hit the issue of 'different options needed for the underlying
package OS modules' until we added the lock option to the yum module.
This is NOT a change to the package action and can happen again for
any/all other package OS modules that it calls in the end, since it
cannot currently validate arguments nor be selective on which ones it
passes, it is only useful for the 'lowest common denominator' set of
options.

--
----------
Brian Coca