RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
After updating nfs-utils, NFS server fails to start at boot.


Version-Release number of selected component (if applicable):
Update from  1.3.0 to 1.3.0-0.8


How reproducible:


Steps to Reproduce:
1. Install update
2. reboot
3. systemctl status nfs-server

Actual results:
NFS service fails to start at boot, but can be started manually after boot.

Expected results:
NFS service starts at boot.

Additional info:
NFS started at boot before the update. After the update, journalctl shows:

Cannot add dependency job for unit nfs.target, ignoring: Unit nfs.target failed to load: No such file or directory.

The problem is that, when nfs-server was enabled originally, the link was placed in /etc/systemd/system/nfs.target.wants. The update removed nfs.target, so the service is never started.

Disabling and re-enabling re-links nfs-server to /etc/systemd/system/multi-user.target.wants. 

The update should have taken care of moving the link over, rather than just just leaving NFS in a broken state. It should have also removed the dead link  /etc/systemd/system/multi-user.target.wants/nfs.target.

*** This bug has been marked as a duplicate of bug 1203765 ***

Can we please not close tickets as duplicates of tickets that everyone else cannot see?  How are affected users supposed to be able to track a bug's status if it's in an access denied ticket?

So what is the status of 1203765 since it is marked private and I cannot access it but I have experienced the problem associated with the broken link?

(In reply to Bill Muller from comment #4)
> So what is the status of 1203765 since it is marked private and I cannot
> access it but I have experienced the problem associated with the broken link?

CLOSED DUPLICATE of bug 1171603
bug 1171603 Status: CLOSED ERRATA which you should be able see.

*** This bug has been marked as a duplicate of bug 1171603 ***