Bug 1776282

Summary: anaconda requires more memory in 8.1
Product: Red Hat Enterprise Linux 8 Reporter: adam winberg <adam.winberg>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: jkonecny, jstodola
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-14 15:02:28 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 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 ***