This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1022641 - systemd is killing puppetagent
systemd is killing puppetagent
Product: Fedora
Classification: Fedora
Component: puppet (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jeroen van Meeuwen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-10-23 13:06 EDT by Jimmy Dorff
Modified: 2015-02-17 12:47 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:47:32 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Log showing puppet installing packages without any problems, then systemd kills it and causes rpmdb problem (2.48 KB, text/plain)
2013-10-23 13:06 EDT, Jimmy Dorff
no flags Details

  None (edit)
Description Jimmy Dorff 2013-10-23 13:06:32 EDT
Created attachment 815489 [details]
Log showing puppet installing packages without any problems, then systemd kills it and causes rpmdb problem

Description of problem:
While puppetagent is installing a large number of packages, systemd kills it.

Version-Release number of selected component (if applicable):

How reproducible:
Frequently occurring on a number of puppet managed Fedora hosts

Steps to Reproduce:
1. Install Fedora
2. Have puppetagent do much work, in my case installing a large number of rpms
3. Systemd says puppet "timed out" and kills it. This can also kill rpm transactions and result in broken rpmdb

Actual results:
puppet agent run is interrupted 

Expected results:
puppet agent run completes.

Additional info:
puppet code in this case is trivial, just installing a list of packages
Comment 1 Jimmy Dorff 2013-10-23 13:14:24 EDT
I suspect this either requires a change to the puppetagent systemd unit configuration or is a bug in systemd. Not sure I can determine which.
Comment 2 Fedora End Of Life 2015-01-09 15:20:51 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2015-02-17 12:47:32 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.