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 1776282 - anaconda requires more memory in 8.1
Summary: anaconda requires more memory in 8.1
Keywords:
Status: CLOSED DUPLICATE of bug 1781517
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-25 12:25 UTC by adam winberg
Modified: 2020-02-14 15:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-14 15:02:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description adam winberg 2019-11-25 12:25:52 UTC 
Description of problem:
When doing network install with the 8.1 pxe images the installation freezes if the server has less than 3G RAM. Our standard/minimal setup is 2G RAM which works fine with the 8.0 images. 




Version-Release number of selected component (if applicable):
anaconda-29.19.1.13-1.el8

How reproducible:
Always

Steps to Reproduce:
1. Create VM with 1 cpu, 2G RAM
2. Network/PXE boot with RHEL 8.1 PXE images
3. 

Actual results:
Installation freezes while downloading packages

Expected results:


Additional info:
The installation halts/freezes while downloading packages. We are using a kickstart file which results in 621 packages being downloaded. Installation target is VMware Vsphere 6.7.

Increasing RAM to 3G solves the problem, using the RHEL 8.0 PXE images also solves the problem (which is what we have done now).
Comment 1 Jiri Konecny 2020-01-17 16:18:35 UTC 
Hello,

Could you please provide us installation logs? You can find them in /tmp/*.log.
Comment 2 Jan Stodola 2020-01-20 12:18:26 UTC 
This could have the same root cause as described in bug 1781517.
Comment 3 adam winberg 2020-01-20 12:25:47 UTC 
The installation freezes so I don't know how I could collect logs from /tmp/. But it does indeed sound very similar to the bug mentioned in #2.
Comment 4 Jan Stodola 2020-02-12 14:13:57 UTC 
Adam,
could you please switch to tty2 (Ctrl+Alt+F2) and run the following command when the installer starts to download the packages?

# grep "download location" /tmp/packaging.log

If the download location is /tmp or /, it's the same problem as described in bug 1781517 and we can close this bug as a duplicate.
Thanks
Comment 5 adam winberg 2020-02-14 06:51:20 UTC 
I tried but that does not work:

bash: grep: command not found

There are very few commands available to me in this shell, no grep, no cat, no ls, nothing that could help med read the log file.
Comment 6 Jan Stodola 2020-02-14 10:34:40 UTC 
That's weird, grep/cat/ls are available in the installation environment and you should see this:

[anaconda root@localhost /]# grep "download location" /tmp/packaging.log
11:23:44,584 INF packaging.log: Mountpoint /mnt/sysimage picked as download location
[anaconda root@localhost /]#

I wonder what the following command says:
[anaconda root@localhost /]# echo $PATH
/bin:/sbin:/usr/bin:/usr/sbin:/mnt/sysimage/sbin:/mnt/sysimage/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:
[anaconda root@localhost /]#
Comment 7 Jiri Konecny 2020-02-14 13:33:05 UTC 
Hi Adam,

Could you please tell us how are you getting into the console or give us screenshot? I think you are not in the installation environment for some reason.
Comment 8 adam winberg 2020-02-14 13:56:16 UTC 
I switch to tty2 (ctrl+alt+f2) and get a shell. It's the only tty with a shell. 

Don't think i had 'echo' either, and no directories at all. Maybe I was in a chrooted env or something?

Unfortunately that machine is dead now so I can't give any screenshots or test further. We have an automated install process so changing install images and locations is a bit of work and potentially breaking for users requesting new servers.  But I will give it another go.
Comment 9 adam winberg 2020-02-14 14:21:44 UTC 
ok, so I managed to get the download location, and it is in fact "/" ("Mountpoint / picked as download location"). 

Thing is, when the installation crashes TTY2 becomes pretty much unusable. In some instances it's simply not there, in other instances commands disappear (which happened to me before) and you are in a real weird state. So I had to be real quick to execute the grep command before the installation crashes. 

Looking at the download info on TTY1, it only tries to download 621RPMS/416.51MiB.
Comment 10 Jan Stodola 2020-02-14 15:02:28 UTC 
Thanks a lot for the log message. So this is the same problem as described in bug 1781517, which will be fixed in RHEL-8.2.

When the installation crashes, the system is in a really weird state, there could even be a kernel panic.

I'm closing this bug as a duplicate of 1781517.

*** This bug has been marked as a duplicate of bug 1781517 ***
Note You need to log in before you can comment on or make changes to this bug.