Bug 2469013 - Installation of the system failed: rsync failure of error code 23
Summary: Installation of the system failed: rsync failure of error code 23
Keywords:
Status: CLOSED DUPLICATE of bug 2412427
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 44
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nathan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-11 09:54 UTC by greenscarf005
Modified: 2026-08-31 23:42 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-07-16 09:32:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description greenscarf005 2026-05-11 09:54:19 UTC
Installation of the system failed: 소프트웨어 160% 설치 중 org.fedoraproject.Anaconda.PayloadInstallationError: Failed to install image: process '['rsync', '-pogAXtlHrDx', '--stats', '--info=flist2,name,progress2', '--no-inc-recursive', '--exclude', '/dev/', '--exclude', '/proc/', '--exclude', '/tmp/*', '--exclude', '/sys/', '--exclude', '/run/', '--exclude', '/boot/*rescue*', '--exclude', '/boot/loader/', '--exclude', '/boot/efi/', '--exclude', '/boot/grub2/', '--exclude', '/etc/sysconfig/', '--exclude', '/usr/lib/grub/', '--exclude', '/etc/machine-id', '--exclude', '/etc/machine-info', '/run/install/sources/mount-0000-live_os_image/', '/mnt/sysroot']' exited with status 23

---[ System & Environment Information ]---
OS: Fedora Linux 44 (KDE Plasma Desktop Edition)
Anaconda version: 44.30
Anaconda UI version: 68

Comment 1 Nathan 2026-05-12 09:52:50 UTC
Fix on Anaconda installer: https://github.com/rhinstaller/anaconda/pull/7059

Comment 2 Nathan 2026-05-20 07:17:14 UTC
The bugfix has been merged into the Anaconda main branch

Comment 3 Adam Williamson (Red Hat non-Fedora) 2026-05-27 16:00:15 UTC
RHBZ bugs should only be closed when the fix is in a Fedora package and the package goes stable. In this case, that happened yesterday: https://bodhi.fedoraproject.org/updates/FEDORA-2026-bc3fb7688c . The correct status progress is:

POST - when a fix is submitted upstream but not yet in a downstream update
MODIFIED - when a fix is in a downstream package but the package is not yet in updates-testing
ON_QA - when the fix reaches updates-testing
CLOSED - when the fix reaches stable

The correct resolution is usually ERRATA for a stable or branched release, or RAWHIDE for Rawhide. CURRENTRELEASE and NEXTRELEASE are only used in unusual situations.

Technically the bug was filed against 44 and is not really resolved in 44 yet, but we don't generally worry about that for anaconda because shipping fixes to stable releases is only of limited use as most installs are run from media that don't get updated. So closing this once the fix reached Rawhide is probably appropriate.

Thanks for the fix!

Comment 4 Adam Williamson (Red Hat non-Fedora) 2026-05-27 16:00:58 UTC
Also, please don't re-assign bugs to yourself unless you are actually in a position to cause the fix to land *downstream*. Submitting a fix upstream is not sufficient to make yourself the downstream assignee.

Comment 5 Adam Williamson (Red Hat non-Fedora) 2026-05-28 06:37:27 UTC
On closer inspection, I'm fairly sure the PR cannot possibly have fixed the installation failure here. Nothing about the rsync output parsing is relevant to the install failure, which was actually due to the rsync process exiting non-zero. Exit code 23 indicates "partial transfer due to error", which to my mind is most likely due to a bad installation medium or target disk. It's impossible to be sure without more logs, though.

Reporter, did you re-try the install? Did it work? If not, can you retry, possibly with a different install medium? If it fails again, can you attach more logs? Thanks.

Comment 6 Katerina Koukiou 2026-05-28 06:56:36 UTC
Fix reverted, https://github.com/rhinstaller/anaconda/pull/7082
Rsync was already being ran with LC_ALL": "C" - the `fix` was not relevant.

Comment 7 Katerina Koukiou 2026-07-16 09:32:01 UTC

*** This bug has been marked as a duplicate of bug 2412427 ***


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