| Summary: | OpenIPMI-modalias RPM owns /var/run/OpenIPMI, but /var/run is tmpfs, need to use tmpfiles | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | giulioo |
| Component: | OpenIPMI | Assignee: | Josef Ridky <jridky> |
| Status: | CLOSED ERRATA | QA Contact: | Rachel Sibley <rasibley> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | jstodola, rasibley |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | OpenIPMI-2.0.19-12.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 01:04:24 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1256306, 1289025, 1305230 | ||
|
Description
giulioo
2016-01-07 14:36:48 UTC
We can simply stop manually installing the directory in %install phase and then we won't have to package it at all. The creation of that directory is handled by systemd just fine. ALL TESTS PASSED Before ========================== # uname -r 3.10.0-327.el7.x86_64 # rpm -qa|grep OpenIPMI OpenIPMI-libs-2.0.19-11.el7.x86_64 OpenIPMI-2.0.19-11.el7.x86_64 # rpm -ql OpenIPMI-modalias /etc/modprobe.d/OpenIPMI.conf /var/run/OpenIPMI # rpm -V OpenIPMI-modalias missing /var/run/OpenIPMI After ========================== # uname -r 3.10.0-408.el7.x86_64 # rpm -qa|grep OpenIPMI OpenIPMI-libs-2.0.19-14.el7.x86_64 OpenIPMI-2.0.19-14.el7.x86_64 OpenIPMI-modalias-2.0.19-14.el7.x86_64 # rpm -ql OpenIPMI-modalias /usr/lib/modprobe.d/OpenIPMI.conf # rpm -V OpenIPMI-modalias # Moving back to Verified State as it was incorrectly moved back to Assigned when switching the package owner. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2225.html |