Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1511943 - 7.4 kmod weak-modules --dry-run fails for oracle user [rhel-7.4.z]
Summary: 7.4 kmod weak-modules --dry-run fails for oracle user [rhel-7.4.z]
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kmod
Version: 7.4
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Yauheni Kaliuta
QA Contact: Ziqian SUN (Zamir)
Marie Dolezelova
Depends On: 1510058
TreeView+ depends on / blocked
Reported: 2017-11-10 13:28 UTC by Oneata Mircea Teodor
Modified: 2017-11-30 19:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the working directory for the kmod /sbin/weak-modules script was writable only for the root user. Consequently, the script did not work on Oracle systems which use their own users. This update moves the working directory from the /lib/modules/<kernel version>/weak-updates location to the location under the /tmp directory for a dry-run invocation. As a result, the working directory is now writable even for a non-root user, and the kmod /sbin/weak-modules script works as expected on Oracle systems.
Clone Of: 1510058
Last Closed: 2017-11-30 16:09:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3326 normal SHIPPED_LIVE kmod bugfix 2017-11-30 20:20:00 UTC

Description Oneata Mircea Teodor 2017-11-10 13:28:00 UTC
This bug has been copied from bug #1510058 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 14 errata-xmlrpc 2017-11-30 16:09:34 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.