Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1235558

Summary:	[atomic] OOM with 1024 MB RAM (squashfs includes ostree content)
Product:	Red Hat Enterprise Linux 7	Reporter:	Radek Vykydal <rvykydal>
Component:	rhel-server-atomic	Assignee:	Colin Walters <walters>
Status:	CLOSED WONTFIX	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.1	CC:	atodorov, dwalsh, fdeutsch, jeder, release-test-team-automation, walters
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1202278	Environment:
Last Closed:	2016-08-19 21:48:14 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:
Bug Depends On:	1202278
Bug Blocks:	1219619, 1252599

Comment 2 Radek Vykydal 2015-06-25 08:04:22 UTC

(In reply to Radek Vykydal from comment #0)
 
> --- Additional comment from Radek Vykydal on 2015-06-25 03:37:07 EDT ---
> 
> We've added the support in lorax to be ready for whatever approach we decide
> to follow. I'll clone this bz for rhel-server-atomic to track the issue
> further (on the level of iso compose, and anaconda support for ostree
> content outside installer image eventually)

One very simple approach would be to use inst.repo= boot option to override ostreesetup --url option in case of Atomic installation. But it is just ad hoc solution to enable PXE (http) installations (all other ostreesetup options would be taken from interactive-defaults.ks, ie bound to installer image).

Comment 3 Alexander Todorov 2015-06-26 07:34:16 UTC

Can we add interactive-defaults.ks to the ostree and make anaconda look for it into a well known location under inst.repo ? Much like it does for updates.img. 

This will also blend nicely if we decide to have Atomic trees similar to RHEL ones (with ostree, install media, PXE boot images, etc). 

The other approach would be to have a custom install class for anaconda with all the defaults.

Comment 4 Colin Walters 2015-09-17 21:03:14 UTC

This one needs work in rpm-ostree-toolbox to take advantage of the lorax changes that are now in 7.2 to keep the content outside of the squashfs, but still embed it in the ISO.