Bug 1552976 - nfs-utils has a scriptlet failure in install env
Summary: nfs-utils has a scriptlet failure in install env
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-08 00:50 UTC by Kevin Fenzi
Modified: 2018-04-15 02:40 UTC (History)
4 users (show)

Fixed In Version: nfs-utils-2.3.1-7.rc1.fc28
Clone Of:
Environment:
Last Closed: 2018-04-15 02:40:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Fenzi 2018-03-08 00:50:39 UTC
Affecting both rawhide and f28, we see: 

Non-fatal <unknown> scriptlet failure in rpm package nfs-utils\n
018-03-07 22:18:23,291 WARNING pylorax.dnfhelper: Non-fatal <unknown> scriptlet failure in rpm package nfs-utils

when installed in the installer env (basically a chroot). 

This seems to be caused by the triggerin scriptlet: 
triggerin scriptlet (using /bin/sh) -- nfs-utils > 1:2.1.1-3
/bin/systemctl try-restart gssproxy

warning: %triggerin(nfs-utils-1:2.3.1-5.fc28.x86_64) scriptlet failed, exit status 1
System has not been booted with systemd as init system (PID 1). Can't operate.

Comment 1 Steve Dickson 2018-04-02 15:18:55 UTC
In the spec file there is a '%{?systemd_requires}'
which I thought requires systemd to be installed. 

How you getting around that?

Comment 2 Kevin Fenzi 2018-04-02 15:30:18 UTC
This is in the installer when it's creating release images. 

ie, see: 
https://koji.fedoraproject.org/koji/taskinfo?taskID=26117283

Then look at root.log: 
https://kojipkgs.fedoraproject.org//work/tasks/7283/26117283/root.log

DEBUG util.py:439:  Running in chroot, ignoring request: try-restart
DEBUG util.py:439:  Running in chroot, ignoring request: try-restart
DEBUG util.py:439:  Installed: nfs-utils-1:2.3.1-5.rc1.fc28.armv7hl

try-restart makes no sense in this context. The "system" is a chroot, it's not booted so you cannot talk to systemd and restarting something in it would make no sense. 

If you really do need to try and restart that service in other cases, the best thing here would likely be to just add: 

"|| :"

to the end of the command so it doesn't ever exit 1, ie: 
systemctl try-restart gssproxy || :

Comment 3 Fedora Update System 2018-04-09 14:52:50 UTC
nfs-utils-2.3.1-6.rc1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-3d22839756

Comment 4 Fedora Update System 2018-04-10 22:50:45 UTC
nfs-utils-2.3.1-6.rc1.fc28 has been pushed to the Fedora 28 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-2018-3d22839756

Comment 5 Fedora Update System 2018-04-11 15:57:15 UTC
nfs-utils-2.3.1-7.rc1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-5f49d4050a

Comment 6 Fedora Update System 2018-04-11 22:59:52 UTC
nfs-utils-2.3.1-7.rc1.fc28 has been pushed to the Fedora 28 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-2018-5f49d4050a

Comment 7 Fedora Update System 2018-04-15 02:40:10 UTC
nfs-utils-2.3.1-7.rc1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


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