Bug 2144179

Summary: Unable to start nfs-server.service - nfs-convert.service not found
Product: [Fedora] Fedora Reporter: Indy <fireballiso>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 37CC: jorton, linux, luk.claes, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: nfs-utils-2.6.2-2.rc4.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-03 02:01:39 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 Indy 2022-11-19 16:14:56 UTC
Description of problem:
nfs-server doesn't start on boot or manually

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


Steps to Reproduce:
1. As root, run the command systemctl start nfs-server.service
2. (See the error immediately)
3.

Actual results:

Failed to start nfs-server.service: Unit nfs-convert.service not found.

Expected results:

NFS server should start normally.

Additional info:
I upgraded Fedora 35 Server edition to Fedora 37, using the "dnf system-upgrade download --releasever=37" command.

Comment 1 Chris Adams 2022-11-20 02:06:34 UTC
FYI: I worked around this bug by masking the non-existent service system "systemctl mask nfs-convert.service", but that's not really a solution.

Comment 2 Steve Dickson 2022-11-22 18:39:00 UTC
Do these files exist? 

/etc/systemd/system/nfs-blkmap.service.requires/nfs-convert.service
/etc/systemd/system/nfs-idmapd.service.requires/nfs-convert.service
/etc/systemd/system/nfs-mountd.service.requires/nfs-convert.service
/etc/systemd/system/nfs-server.service.requires/nfs-convert.service
/etc/systemd/system/rpc-gssd.service.requires/nfs-convert.service
/etc/systemd/system/rpc-statd-notify.service.requires/nfs-convert.service
/etc/systemd/system/rpc-statd.service.requires/nfs-convert.service

Comment 3 Chris Adams 2022-11-22 19:00:38 UTC
None of those exist on my system. The only reference to nfs-convert.service I can find is the /etc/systemd/system/nfs-convert.service symlink to /dev/null (from doing the systemctl mask).

Comment 4 Indy 2022-11-23 01:53:35 UTC
On my system (upgraded from Fedora 35 to 37), these files exist, and are all links:

/etc/systemd/system/nfs-blkmap.service.requires/nfs-convert.service -> /usr/lib/systemd/system/nfs-convert.service
/etc/systemd/system/nfs-idmapd.service.requires/nfs-convert.service -> /usr/lib/systemd/system/nfs-convert.service
/etc/systemd/system/nfs-mountd.service.requires/nfs-convert.service -> /usr/lib/systemd/system/nfs-convert.service
/etc/systemd/system/rpc-gssd.service.requires/nfs-convert.service -> /usr/lib/systemd/system/nfs-convert.service
/etc/systemd/system/rpc-statd-notify.service.requires/nfs-convert.service -> /usr/lib/systemd/system/nfs-convert.service
/etc/systemd/system/rpc-statd.service.requires/nfs-convert.service -> /usr/lib/systemd/system/nfs-convert.service

This file doesn't exist:

/etc/systemd/system/nfs-server.service.requires/nfs-convert.service

Comment 5 Indy 2022-11-23 03:23:43 UTC
Correction - the links exist, but actual file pointed to by the links doesn't exist.

Comment 6 Joe Orton 2022-11-23 09:35:08 UTC
Same problem here after an F35->37 upgrade, exactly as comment 4, I have broken symlinks at the above paths to a non-existent /usr/lib/systemd/system/nfs-convert.service

Comment 7 Steve Dickson 2022-11-23 15:04:36 UTC
(In reply to Indy from comment #4)
> On my system (upgraded from Fedora 35 to 37), these files exist, and are all
> links:
> 
> /etc/systemd/system/nfs-blkmap.service.requires/nfs-convert.service ->
> /usr/lib/systemd/system/nfs-convert.service
> /etc/systemd/system/nfs-idmapd.service.requires/nfs-convert.service ->
> /usr/lib/systemd/system/nfs-convert.service
> /etc/systemd/system/nfs-mountd.service.requires/nfs-convert.service ->
> /usr/lib/systemd/system/nfs-convert.service
> /etc/systemd/system/rpc-gssd.service.requires/nfs-convert.service ->
> /usr/lib/systemd/system/nfs-convert.service
> /etc/systemd/system/rpc-statd-notify.service.requires/nfs-convert.service ->
> /usr/lib/systemd/system/nfs-convert.service
> /etc/systemd/system/rpc-statd.service.requires/nfs-convert.service ->
> /usr/lib/systemd/system/nfs-convert.service

So the workaround is either remove the above directories or 
do a "systemctl mask nfs-convert.service" until I get a updated 
nfs-utils package.

Comment 8 Steve Dickson 2022-11-23 21:55:28 UTC
Here is a scratch build that should take care of the problem

https://koji.fedoraproject.org/koji/taskinfo?taskID=94470281

Please let me know... tia!

Comment 9 Chris Adams 2022-11-23 23:02:16 UTC
BTW I went back and checked my backups from before upgrading from Fedora 35 to 37, and I did have the nfs*.requires entries. I didn't manually delete them, but they are gone now. Would they have been deleted when I did the systemctl mask nfs-convert.service?

Anyway, I stopped nfs-server.service, unmasked nfs-convert.service, and now nfs-server.service starts normally.

Comment 10 Fedora Update System 2022-11-28 17:56:11 UTC
FEDORA-2022-489cb90723 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-489cb90723

Comment 11 Fedora Update System 2022-11-29 02:31:19 UTC
FEDORA-2022-489cb90723 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-489cb90723`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-489cb90723

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2022-12-03 02:01:39 UTC
FEDORA-2022-489cb90723 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Steve Dickson 2023-07-20 15:33:49 UTC
*** Bug 1937815 has been marked as a duplicate of this bug. ***