Bug 1158466
| Summary: | /var/lib/nfs/statd/state should not be configuration file | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miroslav Suchý <msuchy> |
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | bfields, eddie.kuns, jlayton, steved |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-utils-1.3.3-4.rc1.fc23 nfs-utils-1.3.3-4.rc1.fc22 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-30 21:22:26 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
Miroslav Suchý
2014-10-29 12:56:08 UTC
I ran into this upgrading from Fedora 19 to Fedora 21. Given that state is a binary file, I have no idea what I am supposed to do with state.rpmnew. Just delete it? This is what I have: -rw-r--r--. 1 rpcuser rpcuser 4 Oct 15 2013 state -rw-r--r--. 1 rpcuser rpcuser 0 Nov 4 15:13 state.rpmnew The rpmnew file is 0 length, so I will resolve this by deleting the rpmnew file. But it would be better to not create the file unless there is something meaningful that the user can do. (In reply to Edward Kuns from comment #1) > I ran into this upgrading from Fedora 19 to Fedora 21. Given that state is > a binary file, I have no idea what I am supposed to do with state.rpmnew. > Just delete it? This is what I have: > > -rw-r--r--. 1 rpcuser rpcuser 4 Oct 15 2013 state > -rw-r--r--. 1 rpcuser rpcuser 0 Nov 4 15:13 state.rpmnew > > The rpmnew file is 0 length, so I will resolve this by deleting the rpmnew > file. But it would be better to not create the file unless there is > something meaningful that the user can do. Yes... just delete it. That file can not be overwritten because it keeps state for NFS v3 locking. Deleting the file is just workaround.
Correct fix should be:
diff --git a/nfs-utils.spec b/nfs-utils.spec
index ecd4e2e..2dc63da 100644
--- a/nfs-utils.spec
+++ b/nfs-utils.spec
@@ -274,7 +274,7 @@ fi
%dir %attr(700,rpcuser,rpcuser) %{_sharedstatedir}/nfs/statd
%dir %attr(700,rpcuser,rpcuser) %{_sharedstatedir}/nfs/statd/sm
%dir %attr(700,rpcuser,rpcuser) %{_sharedstatedir}/nfs/statd/sm.bak
-%config(noreplace) %attr(644,rpcuser,rpcuser) %{_statdpath}/state
+%ghost %attr(644,rpcuser,rpcuser) %{_statdpath}/state
%config(noreplace) %{_sharedstatedir}/nfs/xtab
%config(noreplace) %{_sharedstatedir}/nfs/etab
%config(noreplace) %{_sharedstatedir}/nfs/rmtab
1) It is not config. As there is nothing to configurate. It is just data file with some runtime state information.
2) %ghost directive will tell RPM to not install that file, however if it exist, "rpm -qf" will admit ownership of nfs-utils. Additionally if nfs-utils are removed, this file will be removed as well.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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. Still valid. nfs-utils-1.3.3-4.rc1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-8d3d8ebc26 nfs-utils-1.3.3-4.rc1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-66b96dbd3f nfs-utils-1.3.3-4.rc1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update nfs-utils' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-8d3d8ebc26 nfs-utils-1.3.3-4.rc1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update nfs-utils' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-66b96dbd3f nfs-utils-1.3.3-4.rc1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update nfs-utils' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-66b96dbd3f nfs-utils-1.3.3-4.rc1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. nfs-utils-1.3.3-4.rc1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |