puppet and yum lock

[Aaron Addleman]

Hi Everyone,

I am having a problem with installing rpm packages on CentOS using yum. The problem is when another instance of yum is running and a lock is created my module that needs to install a package is unable to proceed.

This problem sounds like a really simple one to solve but I have not found any information on a solution.

Could someone point me in a direction?

Thanks in advance,

Aaron

[Alexander Petrovsky]

Hi!

Did you find out why does it happens? I got the same error, on amazon linux, puppet 3.0.2.

среда, 7 августа 2013 г., 20:08:43 UTC+4 пользователь Aaron Addleman написал:

[Russell Cecala]

Can you install the rpm with yum without puppet? Maybe the rpm you are installing is doing something to cause a deadlock like executing "rpm -i some-package" or "yum install blah-blah" in the %post section of the rpm's spec file.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/83bec188-4bed-42ec-b386-93ebfda4eb8d%40googlegroups.com.

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

[jcbollinger]

On Thursday, December 19, 2013 2:54:39 PM UTC-6, Alexander Petrovsky wrote:

Hi!

Did you find out why does it happens? I got the same error, on amazon linux, puppet 3.0.2.

It is a normal behavior of yum.  Yum uses a lock file to prevent multiple sessions from proceeding contemporaneously.  It needs to do something of the sort to ensure transactional consistency.

Inasmuch as package management is a maintenance procedure, not a routine operation, it is appropriate to consider whether this is even a problem that needs to be resolved.  Otherwise, either Puppet will proceed after the lock is released, or it will fail that run but more than likely succeed on the next one.

There is a related issue that you might want to look into however: some plugins cause yum to hold onto its lock after the actual package manipulations are complete, while it performs additional actions, typically in a separate process.  This behavior can significantly extend locks' duration, so you may want to consider avoiding such plugins.


John