RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1627911 - image builds fail with anaconda consuming all mem and OOM
Summary: image builds fail with anaconda consuming all mem and OOM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.6
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-11 20:42 UTC by Terry Bowling
Modified: 2021-02-15 07:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-15 07:42:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
trimmed anaconda log. the original was 1.7 GB due to repeated error messages (132.81 KB, text/plain)
2018-09-11 20:42 UTC, Terry Bowling
no flags Details
program.log (43.45 KB, text/plain)
2018-09-11 20:45 UTC, Terry Bowling
no flags Details
packaging.log (157.32 KB, text/plain)
2018-09-11 20:46 UTC, Terry Bowling
no flags Details

Description Terry Bowling 2018-09-11 20:42:36 UTC
Created attachment 1482445 [details]
trimmed anaconda log.  the original was 1.7 GB due to repeated error messages

Description of problem:

Builds fail for any type of image (live-iso, qcow2, or ext4 filesystem) with anaconda consuming all memory until OOM events occur.


Version-Release number of selected component (if applicable):

# rpm -q lorax-composer cockpit-composer lorax composer-cli
lorax-composer-19.7.22-1.el7.x86_64
cockpit-composer-0.1.4-1.el7.noarch
lorax-19.7.19-1.el7.x86_64
composer-cli-19.7.22-1.el7.x86_64


How reproducible:

1. Install RHEL 7.6 Beta
2. Enable all beta and htb channels
3. Download 7.6 nightly composer builds
4. setenforce 0
5. enable cockpit and lorax-composer services
6. From Cockpit Composer interface, a simple blueprint with only sshd server added.
7. Build qcow2 image

Comment 2 Terry Bowling 2018-09-11 20:45:44 UTC
Created attachment 1482446 [details]
program.log

Comment 3 Terry Bowling 2018-09-11 20:46:25 UTC
Created attachment 1482447 [details]
packaging.log

Comment 4 Brian Lane 2018-09-11 21:02:41 UTC
16:02:42,689 ERR packaging: No base repo configured

Is the core issue here, lorax-composer doesn't currently support using repos that require certificates (eg. the cdn).

But Anaconda should do a better job of failing here, instead of falling into an error loop it should exit with an error since it is running in cmdline mode.

Comment 9 RHEL Program Management 2021-02-15 07:42:33 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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