Bug 1837947

Summary: pesign.service fails to start
Product: [Fedora] Fedora Reporter: Ryan <stealthcipher>
Component: pesignAssignee: Peter Jones <pjones>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 32CC: mjg59, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 08:40:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ryan 2020-05-20 09:12:48 UTC
Description of problem:
pesign.service fails to start with the following error:

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

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

How reproducible:
test starting or enabling pesign.service...happens every time.

Steps to Reproduce:
1. install pesign
2. try to start or enable service
3. note unit file error message

Actual results:
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

Expected results:
service enabled and started when passing the relevant commands to the unit file

Additional info:
fwupd tries to restart this service during update. by default pesign is not installed, if installed it's going to throw this error when the restart action is tried. There is a bug against fwupd already about trying to restart pesign.service during the update process.

Comment 1 Ryan 2020-11-04 08:40:35 UTC
This has been resolved by later updates to the components in question (fwupd and pesign)