When running on pulp3: 1. create a repo and remote pointing to https://fixtures.pulpproject.org/rpm-advisory-no-update-date/repodata/ 2. sync the remote, create a publication and distribution 3. examine the repodata, look for the Bird erratum section of the updateinfo xml: <update from="errata" status="stable" type="security" version="1"> <id>RHEA-2012:0056</id> <title>Bird_Erratum</title> <issued date="2013-01-27 16:08:08"/> <updated date="0693-02-18 07:00:00"/> Note that the date is nonsense. this causes an issue for things trying to consumer this date, such as katello or another pulp server trying to sync This is also a problem for the migration and the repositories that get created from it. We'll need to upgrade to pulp-rpm 3.9 for the fix
Connecting redmine issue https://projects.theforeman.org/issues/31785 from this bug
Moving to POST, NOTE, this requires: * katello cherry pick (from associated foreman issue) * new rubygem-pulp_rpm_client build (3.9.0) * new python3-pulp-rpm build (3.9.0)
Verified on 6.9.0 snap 17.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:1313