|Summary:||nfs v3 locking broken after rpcbind updates|
|Product:||[Fedora] Fedora||Reporter:||Roderick Johnstone <rmj>|
|Component:||rpcbind||Assignee:||Steve Dickson <steved>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2017-08-08 19:38:14 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Roderick Johnstone 2017-02-06 17:36:47 UTC
Description of problem: After an update to rpcbind on a Fedora 24 nfs server, nfs v3 clients can no longer obtain locks. Version-Release number of selected component (if applicable): rpcbind-0.2.3-17.rc2.fc24.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Update rpcbind on Fedora 24 nfs server. 2. Try to obtain a file lock on nfs client mounting exported filesystem with nfsv3. 3. Actual results: nfs v3 file locking is broken on nfs client: eg dovecot report: Feb 5 08:29:22 nfsclient dovecot: imap(<user>): Error: fcntl(write-lock) locking failed for file /home/<user>/mail/.imap/Drafts/dovecot.index.log: No locks available Expected results: File locking works on nfs client. Additional info: On nfs server: yum.log contains Feb 04 03:27:16 Updated: rpcbind-0.2.3-17.rc2.fc24.x86_64 journalctl -u rpc-statd Feb 04 03:27:16 nfsserver systemd: Stopping NFS status monitor for NFSv2/3 locking.... Feb 04 03:27:16 nfsserver systemd: Stopped NFS status monitor for NFSv2/3 locking.. Feb 04 03:27:16 nfsserver systemd: Dependency failed for NFS status monitor for NFSv2/3 locking.. Feb 04 03:27:16 nfsserver systemd: rpc-statd.service: Job rpc-statd.service/start failed with result 'dependency'. Similar symptom to rpc.statd problem in #1372463 but different error being logged.
Comment 1 Fedora End Of Life 2017-07-26 00:14:54 UTC
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2017-08-08 19:38:14 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.