Bug 21437 - Puppet can't run because of incorrect unit file shipped in the RPM
Summary: Puppet can't run because of incorrect unit file shipped in the RPM
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High major
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
Whiteboard: MGA6TOO,
Depends on:
Reported: 2017-08-02 16:37 CEST by Remco Rijnders
Modified: 2017-08-21 20:53 CEST (History)
2 users (show)

See Also:
Source RPM: puppet-4.2.1-4.mga6.src.rpm
Status comment:


Description Remco Rijnders 2017-08-02 16:37:39 CEST
Description of problem:
puppet won't run properly because of incorrect unit files.

The puppet.service file shipped in the rpm contains the following:
Description=Puppet agent
After=basic.target network.target

ExecStart=/opt/puppetlabs/puppet/bin/puppet agent $PUPPET_EXTRA_OPTS --no-daemonize


The ExecStart setting is obviously wrong. It looks like the SOURCE100 source from the spec file is never applied in the package built. It also look like SOURCE101, puppetmaster.service has the same issue.
Remco Rijnders 2017-08-02 16:37:54 CEST

CC: (none) => luigiwalser

Comment 1 Rémi Verschelde 2017-08-02 16:39:16 CEST
Assigning to sysadmins as puppet has no registered maintainer, but we need this fixed anyway before we can upgrade our own puppet-based infra to Mageia 6.

Assignee: bugsquad => sysadmin-bugs
Priority: Normal => High

David Walser 2017-08-20 23:34:11 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=21577
CC: luigiwalser => (none)

Marja Van Waes 2017-08-21 20:53:49 CEST

CC: (none) => guillomovitch, marja11
Version: 6 => Cauldron
Whiteboard: (none) => MGA6TOO,

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