Bug 1526715

Summary: Setting SERVICE=no results in a failed status of the man-db-cache-update service
Product: [Fedora] Fedora Reporter: Sam Varshavchik <mrsam>
Component: man-dbAssignee: Nikola Forró <nforro>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: jchaloup, nforro
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: man-db-2.7.6.1-8.fc26 man-db-2.7.6.1-10.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-26 16:31:55 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 Sam Varshavchik 2017-12-16 16:18:46 UTC
Description of problem:

When SERVICE=no is set in /etc/sysconfig/man-db, the one-shot systemd job will fail.

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

man-db-2.7.6.1-9.fc27.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Set SERVICE=no in /etc/sysconfing/man-db
2. Reload systemd
3. Reboot

Actual results:

Perusing systemd logs after the reboot reports that the job has failed.

This can also be reproduced without rebooting by starting the one-shot job manually with "systemctl start":

● man-db-cache-update.service
   Loaded: loaded (/usr/lib/systemd/system/man-db-cache-update.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-12-16 11:11:36 EST; 5min ago
  Process: 2856 ExecStart=/bin/sh -c [ "$SERVICE" != "no" ] && /usr/bin/mandb $OPTS (code=exited, status=1/FAILURE)
 Main PID: 2856 (code=exited, status=1/FAILURE)

Dec 16 11:11:36 thinkpad systemd[1]: Starting man-db-cache-update.service...
Dec 16 11:11:36 thinkpad systemd[1]: man-db-cache-update.service: Main process exited, code=exited, status=1/FAILURE
Dec 16 11:11:36 thinkpad systemd[1]: Failed to start man-db-cache-update.service.
Dec 16 11:11:36 thinkpad systemd[1]: man-db-cache-update.service: Unit entered failed state.
Dec 16 11:11:36 thinkpad systemd[1]: man-db-cache-update.service: Failed with result 'exit-code'.

Expected results:

When configured thusly, the oneshot job should just do nothing and quietly go away.

Additional info:

The command line results in the executed command exiting with a non-zero exit status, when SERVICE=no. This gets interpreted as a failed job.

Comment 2 Fedora Update System 2017-12-19 16:59:45 UTC
man-db-2.7.6.1-10.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-d01a7839c0

Comment 3 Fedora Update System 2017-12-19 16:59:50 UTC
man-db-2.7.6.1-8.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-13af4c1fb1

Comment 4 Fedora Update System 2017-12-19 22:49:45 UTC
man-db-2.7.6.1-10.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-d01a7839c0

Comment 5 Fedora Update System 2017-12-19 23:44:03 UTC
man-db-2.7.6.1-8.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-13af4c1fb1

Comment 6 Fedora Update System 2017-12-26 16:31:55 UTC
man-db-2.7.6.1-8.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2017-12-28 02:51:05 UTC
man-db-2.7.6.1-10.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.