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 1776410 - Package "X" from local repository "Y" has incorrect checksum . Reposync does not transfer all RPMs.
Summary: Package "X" from local repository "Y" has incorrect checksum . Reposync does ...
Keywords:
Status: CLOSED DUPLICATE of bug 1775434
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf-plugins-core
Version: 8.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: Marek Blaha
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-25 16:15 UTC by Justin Pierce
Modified: 2024-03-25 15:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-09 11:36:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Justin Pierce 2019-11-25 16:15:20 UTC 
Description of problem:
After a reposync of rhel-8 baseos & appstream repositories, I am still unable to install mariadb due to missing files/checksum errors.



Version-Release number of selected component (if applicable):
4.2.7
  Installed: dnf-0:4.2.7-7.el8_1.noarch at Tue Oct 29 16:41:41 2019
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at Mon Oct 21 12:28:04 2019

  Installed: rpm-0:4.14.2-25.el8.x86_64 at Tue Oct 29 16:41:36 2019
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at Wed Aug  7 13:32:37 2019



How reproducible:
100%

Steps to Reproduce:
1. Run a rhel8 ubi image
2. Reposync the pulp.dist baseos & appstream rhel-8 repositories
3. Attempt to use those repositories to install mariadb

Actual results:
Error opening file for checksum: /4.2/rhel-8-appstream-rpms/rhel-8-appstream-rpms/Packages/p/perl-IO-Socket-IP-0.39-5.el8.noarch.rpm
Package "perl-IO-Socket-IP-0.39-5.el8.noarch" from local repository "rhel-8-appstream-rpms" has incorrect checksum
Error opening file for checksum: /4.2/rhel-8-appstream-rpms/rhel-8-appstream-rpms/Packages/p/perl-libnet-3.11-3.el8.noarch.rpm
Package "perl-libnet-3.11-3.el8.noarch" from local repository "rhel-8-appstream-rpms" has incorrect checksum
Error opening file for checksum: /4.2/rhel-8-appstream-rpms/rhel-8-appstream-rpms/Packages/p/perl-Digest-1.17-395.el8.noarch.rpm
Package "perl-Digest-1.17-395.el8.noarch" from local repository "rhel-8-appstream-rpms" has incorrect checksum
Error opening file for checksum: /4.2/rhel-8-appstream-rpms/rhel-8-appstream-rpms/Packages/p/perl-Digest-MD5-2.55-396.el8.x86_64.rpm
Package "perl-Digest-MD5-2.55-396.el8.x86_64" from local repository "rhel-8-appstream-rpms" has incorrect checksum
Error: Some packages from local repository have incorrect checksum


Expected results:
All RPMs & modules should be intact in the local repositories.


Additional info:
Detailed steps:

host$ mkdir artifacts
host$ mkdir 4.2
# Run a ubi image 

host$ sudo podman run -it --rm -v $PWD/artifacts:/artifacts:Z -v $PWD/4.2:/4.2:Z registry.access.redhat.com/ubi8/ubi@sha256:a7209baef64d9a6e8e87cbc2a6f27d402a04cd3750006f1338a2924b4bf585f7 /bin/sh

# reposync baseos  (yum.conf attached to this BZ)
ubi$ dnf -v reposync --download-metadata --setopt=module_platform_id="platform:el8" -c /artifacts/yum.conf -p /4.2/rhel-8-baseos-rpms --delete --arch noarch --arch x86_64 -n --repo rhel-8-baseos-rpms --downloadcomps | tee reposync.1.log

# reposync appstream (yum.conf attached to this BZ)
ubi$ dnf -v reposync --download-metadata --setopt=module_platform_id="platform:el8" -c /artifacts/yum.conf -p /4.2/rhel-8-appstream-rpms --delete --arch noarch --arch x86_64 -n --repo rhel-8-appstream-rpms --downloadcomps | tee reposync.2.log

# Overwrite system yum.conf with yum.install.conf from this BZ
ubi$ cp /artifacts/yum.install.conf /etc/yum.conf

# Installing python36 works great (see attached log)
ubi$ dnf install python36

# Installing mariadb fails (see attached log)
ubi$ dnf install mariadb
Comment 2 Marek Blaha 2019-12-09 11:36:11 UTC 
This is actually a duplicate of the https://bugzilla.redhat.com/show_bug.cgi?id=1775434 bug. The problem is that `dnf reposync --newest-only` is broken with modular repositories.
As a workaround (until the patched version is released) you can drop `-n` option when syncing the appstream repository - at the cost of several gigabytes of storage space.
I tried your use case with patched reposync (https://github.com/rpm-software-management/dnf-plugins-core/pull/375) and I can confirm that the patched version works well and mariadb is installable.

If you disagree with closing this bug as a duplicate, please do not hesitate to reopen it.

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