Description of problem: just installing form netinstall, using updates repository found via closes mirrors. Version-Release number of selected component: anaconda-26.21.11-1 The following was filed automatically by anaconda: anaconda 26.21.11-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/dnfpayload.py", line 923, in install raise payload.PayloadError(msg) File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 437, in run_task self._task(*self._task_args, **self._task_kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 471, in start self.run_task() File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 303, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 303, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/install.py", line 363, in doInstall installation_queue.start() File "/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/threads.py", line 251, in run threading.Thread.run(self) pyanaconda.payload.PayloadError: Payload error - DNF installation has ended up abruptly: error reading package headerTraceback (most recent call last): File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/dnfpayload.py", line 276, in do_transaction base.do_transaction(display=display) File "/usr/lib/python3.6/site-packages/dnf/base.py", line 677, in do_transaction self.transaction._populate_rpm_ts(self._ts) File "/usr/lib/python3.6/site-packages/dnf/transaction.py", line 196, in _populate_rpm_ts hdr = tsi.installed._header File "/usr/lib/python3.6/site-packages/dnf/package.py", line 87, in _header return dnf.rpm._header(self.localPkg()) File "/usr/lib/python3.6/site-packages/dnf/rpm/__init__.py", line 70, in _header return ts.hdrFromFdno(fdno) File "/usr/lib64/python3.6/site-packages/rpm/transaction.py", line 175, in hdrFromFdno raise rpm.error("error reading package header") _rpm.error: error reading package header Additional info: addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: BOOT_IMAGE=/fc26/vmlinuz inst.stage2=https://mirrors.nic.cz/fedora/linux/releases/26/Everything/x86_64/os/ acpi_enforce_resources=lax libata.atapi_passthru16=0 quiet rd.blackist=nouveau executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.11.8-300.fc26.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 26
Created attachment 1312290 [details] File: anaconda-tb
Created attachment 1312291 [details] File: anaconda.log
Created attachment 1312292 [details] File: dnf.librepo.log
Created attachment 1312293 [details] File: environ
Created attachment 1312294 [details] File: hawkey.log
Created attachment 1312295 [details] File: lsblk_output
Created attachment 1312296 [details] File: lvm.log
Created attachment 1312297 [details] File: nmcli_dev_list
Created attachment 1312298 [details] File: os_info
Created attachment 1312299 [details] File: program.log
Created attachment 1312300 [details] File: storage.log
Created attachment 1312301 [details] File: syslog
Created attachment 1312302 [details] File: ifcfg.log
Created attachment 1312303 [details] File: packaging.log
I found the issue. It was due to anaconda reusing RPMs downloaded in previous attempt to install which failed on nouveau kernel crash. The data were downloaded to /home/dnf-something-cache-dir but were never deleted or revalidated. There were about 10 files with zero lenght that weren't redownloaded. My first approach was to use other online repos but the error still persisted until I found, checked and removed that cache folder manually. If I wasn't reusing /home partition, this wouldn't have happened I suppose. If the folder cannot be deleted, I believe it should not be just appended with new files without rechecking the contents anyhow. It is not unusual that the installation is aborted for user's or other reason.
Similar problem has been detected: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: initrd=/images/pxeboot/initrd.img inst.stage2=hd:LABEL=F26 quiet BOOT_IMAGE=/images/pxeboot/vmlinuz hashmarkername: anaconda kernel: 4.11.8-300.fc26.x86_64 package: anaconda-26.21.11-1 product: Fedora reason: pyanaconda.payload.PayloadError: Payload error - DNF installation has ended up abruptly: Transaction check error: release: Cannot get release name. version: 26
(In reply to Tomas Dolezal from comment #15) > I found the issue. It was due to anaconda reusing RPMs downloaded in > previous attempt to install which failed on nouveau kernel crash. > The data were downloaded to /home/dnf-something-cache-dir but were never > deleted or revalidated. There were about 10 files with zero lenght that > weren't redownloaded. I was not able to reproduce the issue, in my case rpm files with zero-length (or truncated manually) were re-downloaded because the checksum didn't match. Anyway, I think we can safely clear the cache dir before installing the packages.
https://github.com/rhinstaller/anaconda/pull/1218
Similar problem has been detected: I was installing fedora 26 via netinstaller. After all 4 GB of software been downloaded, this occurred!! 2 Times!! I wish I knew wich package did this so I will not install it next time. addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-dvd-x86_64-26 rd.live.check quiet hashmarkername: anaconda kernel: 4.11.8-300.fc26.x86_64 package: anaconda-26.21.11-1 product: Fedora reason: pyanaconda.payload.PayloadError: Payload error - DNF installation has ended up abruptly: Transaction check error: release: Cannot get release name. version: 26
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.
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.