Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 2105047

Summary: Error 'modulemd-yaml-error-quark' while synchronizing fedora modular repository on Satellite 6.10.
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lai <ltran>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.10.3CC: dalley, iballou, matthew.lesieur, osousa
Target Milestone: 6.11.1Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libmodulemd2-2.12.1-1.el7pc Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2070168 Environment:
Last Closed: 2022-07-27 17:27:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Lai 2022-07-18 18:03:26 UTC 
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
Comment 3 Matthew LeSieur 2022-07-18 18:12:06 UTC 
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/
Comment 8 errata-xmlrpc 2022-07-27 17:27:10 UTC 
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