Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1170659 - katello-installer may fail on machines with low RAM
Summary: katello-installer may fail on machines with low RAM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Evgeni Golov
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1359873 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-04 14:49 UTC by Kedar Bidarkar
Modified: 2020-04-15 14:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:44:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15696 0 Normal Closed katello-installer may fail on machines with low RAM 2020-05-13 02:08:41 UTC

Description Kedar Bidarkar 2014-12-04 14:49:12 UTC 
Created attachment 964695 [details]
katello-installer fails when running on less RAM

Description of problem:

Trying to install a katello+foreman setup may fail on machines with low RAM.

RAM = 1 GB


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

How reproducible:
sometimes.

Steps to Reproduce:
1. Try running katello-installer with no swap and less RAM.
2.
3.

Actual results:
katello-installer configuration may fail.

Expected results:
should pass or give a proper message.

Additional info:
Comment 1 Kedar Bidarkar 2014-12-04 14:54:41 UTC 
Steps to Reproduce:
1. Try running katello-installer with less RAM.
Comment 3 Jitendra Yejare 2015-03-17 10:27:01 UTC 
I am getting following errors while installing Katello Installer for Satellite6 S6C2 on RHEL 7.1 64 bit machine having 2 GB(low) RAM:

Logs from /var/log/katello-installer/katello-installer.log:

[ERROR 2015-03-16 04:53:07 main]  /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: Command exceeded timeout
[ERROR 2015-03-16 04:53:08 main]  /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Command exceeded timeout
[ERROR 2015-03-16 05:01:36 main] Repeating errors encountered during run:
[ERROR 2015-03-16 05:01:36 main]  /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: Command exceeded timeout
[ERROR 2015-03-16 05:01:36 main]  /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Command exceeded timeout

However, post-installation, I am able to browse and login to Satellite6 web UI.
Comment 6 Stephen Benjamin 2016-08-23 17:22:59 UTC 
*** Bug 1359873 has been marked as a duplicate of this bug. ***
Comment 7 Bryan Kearney 2016-09-02 16:05:10 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15696 has been resolved.
Comment 10 Evgeni Golov 2017-08-09 11:31:40 UTC 
VERIFIED

Version Tested:
Satellite-6.3 Snap 10
foreman-installer-katello-3.4.4-1.el7sat.noarch
satellite-installer-6.3.0.3-1.beta.el7sat.noarch
katello-installer-base-3.4.4-1.el7sat.noarch
foreman-installer-1.15.2-1.el7sat.noarch

# free -m
              total        used        free      shared  buff/cache   available
Mem:           3694         209        1545           8        1939        3105
Swap:          1535           0        1535

# satellite-installer --scenario satellite
This system has less than 8 GB of total memory. Please have at least 8 GB of total ram free before running the installer.
Comment 11 Craig Donnelly 2017-08-09 12:13:39 UTC 
I realize that this BZ is extremely old, but should this not reflect a requirement of 12GB to match documentation at this point?
Comment 12 Evgeni Golov 2017-08-09 12:33:03 UTC 
(In reply to Craig Donnelly from comment #11)
> I realize that this BZ is extremely old, but should this not reflect a
> requirement of 12GB to match documentation at this point?

Indeed, https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/preparing_your_environment_for_installation#hardware_requirements documents the minimun as 12G now (I was not aware of that).

However, we could debate whether this is the same "minimum". The 8G the installer is talking about comes from upstream and is the minimal recommendation to run Katello/Satellite with a couple of clients without going OOM on the smallest action. For that 8G are perfectly fine. The 12G we document allows for a few more clients (but it's also not enough if you have thousands).

@Toledo, do you have an opinion on that, given you have implemented the feature in the first place?
Comment 13 Chris Roberts 2017-08-09 14:19:49 UTC 
Hi,

Currently our upstream docs say:

8 GB of memory (12 GB highly recommended)

https://theforeman.org/plugins/katello/3.4/installation/index.html

I would file a Downstream Docs BZ to reflect the upstream change.
Comment 14 Satellite Program 2018-02-21 16:44:36 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.

https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.