Bug 1269395
Summary: | yum eats whole memory when running in docker container with OverlayFS | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Tomas Tomecek <ttomecek> |
Component: | yum-utils | Assignee: | Valentina Mukhamedzhanova <vmukhame> |
Status: | CLOSED ERRATA | QA Contact: | Karel Srot <ksrot> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | CC: | james.antill, ksrot, lmiksik, packaging-team-maint, podvody |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | yum-utils-1.1.31-34.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 12:10:44 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
Tomas Tomecek
2015-10-07 08:13:55 UTC
Debug output ``` Step 8 : RUN yum -d 99 -y install https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm ---> Running in fb9ce68e428b Loading "ovl" plugin Loading "product-id" plugin Loading "search-disabled-repos" plugin Loading "subscription-manager" plugin Updating Subscription Management repositories. Unable to read consumer identity This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Config time: 0.050 Yum version: 3.4.3 rpmdb time: 0.000 Examining /var/tmp/yum-root-YNnqqU/epel-release-7-5.noarch.rpm: epel-release-7-5.noarch Marking /var/tmp/yum-root-YNnqqU/epel-release-7-5.noarch.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package epel-release.noarch 0:7-5 will be installed Checking deps for epel-release.noarch 0:7-5 - u looking for ('config(epel-release)', 'EQ', ('0', '7', '5')) as a requirement of epel-release.noarch 0:7-5 - u looking for ('redhat-release', 'GE', ('0', '7', None)) as a requirement of epel-release.noarch 0:7-5 - u --> Finished Dependency Resolution Dependency Process ending Depsolve time: 0.050 Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: epel-release noarch 7-5 /epel-release-7-5.noarch 24 k Transaction Summary ================================================================================ Install 1 Package Total size: 24 k Installed size: 24 k Downloading packages: Member: epel-release.noarch 0:7-5 - u Adding Package epel-release-7-5.noarch in mode u Running transaction check Transaction check time: 0.001 Running transaction test Transaction test succeeded Transaction test time: 0.001 Running transaction Installing : epel-release-7-5.noarch 1/1 Setting up Package Sacks ovl: Copying up (0) files from OverlayFS lower layer pkgsack time: 2.421 Installed products updated. Verifying : epel-release-7-5.noarch 1/1^C ``` This is caused by the fact that the plugin gets invoked during pre-repository setup hook, and in this particular use-case the repository setup happens too late, because we don't use repository to resolve the package itself: $ yum install -y https://.../some.rpm Valentina is working on a fix which invokes the plugin during 'init' setup hook, which should give stronger guarantee. Note that this still leaves a grey area since if PluginA gets executed *before* ovl, and if PluginA also happens to need to work with Rpmdb in some way, it might still be affected by the underlying copy-up issue. Upstream fix - https://github.com/rpm-software-management/yum-utils/commit/d03fce57c1fa3f9dff6fdd9867cbcaf66df9f841 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-2015-2129.html |