Followed the steps in description for testing. Expected result: Syncing should be completed and successful Actual result: Syncing is complete and is successful # hammer repository info --id 1 Id: 1 Name: module_md_repo Label: module_md_repo Description: Organization: Default Organization Red Hat Repository: no Content Type: yum Mirroring Policy: Content Only Url: https://dl.fedoraproject.org/pub/fedora/linux/updates/35/Modular/x86_64/ Publish Via HTTP: yes Published At: https://<satellite>/pulp/content/Default_Organization/Library/custom/my-prod/module_md_repo/ Relative Path: Default_Organization/Library/custom/my-prod/module_md_repo Download Policy: immediate Ignorable Content Units: HTTP Proxy: HTTP Proxy Policy: global_default_http_proxy Product: Id: 1 Name: my-prod GPG Key: Sync: Status: Success Last Sync Date: 1 minute Created: 2022/07/18 17:51:05 Updated: 2022/07/18 17:51:08 Content Counts: Packages: 1692 Source RPMS: 0 Package Groups: 0 Errata: 23 Module Streams: 70 Verified on 6.11.1 snap 2 with libmodulemd-2.13.0-1.el8.x86_64
At some point, Fedora removed the "modulemd-obsoletes" document types from the Fedora 35 modular repositories, so synchronizing this repository will succeed regardless. The Fedora 36 Modular repository contains "modulemd-obsoletes" document type, so you should test there instead. https://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/
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 (Satellite 6.11.1 Async Bug Fix Update), 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/RHBA-2022:5742