Bug 1474297 - Unable to install using kickstart with http repo due to incorrect location for dnf.package.cache dir
Summary: Unable to install using kickstart with http repo due to incorrect location fo...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 10:50 UTC by Roland Hermans
Modified: 2018-05-29 12:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:28:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Tail of journalctl -ab output (10.29 KB, text/plain)
2017-07-24 10:50 UTC, Roland Hermans
no flags Details

Description Roland Hermans 2017-07-24 10:50:23 UTC
Created attachment 1303573 [details]
Tail of journalctl -ab output

Description of problem:
To install our Fedora workstations I use a kickstart script that specifies HTTP repositories. When using HTTP repositories, before starting the actual installation of the rpms Anaconda downloads all the rpms to install to a (local) directory named dnf.package.cache. The location of this dnf.package.cache directory is determined by the method _pick_mpoint() in pyanaconda/payload/dnfpayload.py. It incorrectly selects / as most suitable download location.

In our case the download size of the rpms is about 2.7 GB. Dracut has mounted the live install image on / in read/write mode using a filesystem overlay. The image has a size of 8 GB of which about 4.5 GB is used and 3.5 GB is reported as free. However this system only has 4 GB of RAM, which is insufficient to download all the rpm files to the overlay. As a result after downloading around 550 MB the filesystem on / is corrupted and the installation hangs or ends with a fatal error message.

Conclusion: For a filesystem with an overlay the system can report more available free space than what is actually available, so Anaconda cannot rely on the df output for such a filesystem.

Version-Release number of selected component (if applicable):
download.fedoraproject.org mirror of July 24, 2017.

How reproducible:
Success or failure depends on the amount of system RAM, the download size and the free space in the install image. In my case the installation fails with 2, 3 or 4 GB RAM, but succeeds with 8 GB RAM.

Steps to Reproduce:
1. Create a virtual host with 4 GB of RAM.
2. Create a kickstart file to use HTTP repositories and enable sufficient package groups to have a download size of about 2.7 GB.
3. Boot the host via PXE to install the system.

Actual results:
- When installing in graphical mode, the installer hangs after downloading +/- 16% of the packages. The screen is no longer updated, mouse can still be moved.
- When installing in text mode, the installation is aborted with the following message:

Error

The following error occurred while installing. This is a fatal error and
installation will be aborted.

Failed to download 'kernel-modules-4.11.11-300.fc26.x86_64.rpm': 3 - Curl error (23): Failed writing received data to disk/application for http://download.fedoraproject.org/pub/fedora/linux/updates/26/x86_64/k/kernel-modules-4.11.11-300.fc26.x86_64.rpm [Failed writing body (273 != 16384)]

Expected results:
The installation completes successfully without errors.

Additional info:
See attached journal.txt for the relevant part of the log file.

Comment 1 Fedora End Of Life 2018-05-03 08:08:35 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2018-05-29 12:28:00 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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