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 2264172

Summary:	Subscription-manager commands fail with the error 'Module yaml error: Encountered two streams with matching NSVCA'
Product:	Red Hat Satellite	Reporter:	mithun kalyat <mkalyat>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.14.0	CC:	ahumbe, dalley, iballou, osousa, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, PrioBumpGSS, Triaged, WorkAround
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pulp-rpm-3.19.12-1, pulp-rpm-3.23.1-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2272109 2279320 (view as bug list)		Environment:
Last Closed:	2024-06-06 17:02:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description mithun kalyat 2024-02-14 11:14:21 UTC

Description of problem:

Subscription-manager or insights-client commands fail with the below error.

# subscription-manager repos --list
Module yaml error: Encountered two streams with matching NSVCA ant:1.10:820181213135032:5ea3b708:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA scala:2.10:820181213143541:2b79a98f:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA subversion:1.10:820181215112250:a51370e3:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA ant:1.10:820181213135032:5ea3b708:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA scala:2.10:820181213143541:2b79a98f:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA subversion:1.10:820181215112250:a51370e3:x86_64 but differing content

# insights-client
Unable to fetch egg url https://satellite.example.com:443/redhat_access/r/insights/platform/module-update-router/v1/channel?module=insights-core: 500: Internal Server Error. Defaulting to /release
Starting to collect Insights data for client.example.com
Module yaml error: Encountered two streams with matching NSVCA ant:1.10:820181213135032:5ea3b708:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA scala:2.10:820181213143541:2b79a98f:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA subversion:1.10:820181215112250:a51370e3:x86_64 but differing content
Module yaml error: Encountered two streams with matching NSVCA ant:1.10:820181213135032:5ea3b708:x86_64 but differing content

Version-Release number of selected component (if applicable):

Red Hat Satellite 6.14

How reproducible:

We don't have the exact reproducer, but rather some scenarios where this issue occurred.

1) This occurs on upgraded Satellite 6.14 clients.

2) After changing the content view to the default organization view, the problem persists (the issue is not CV-specific).

3) In a few cases, issues arose after updating content views.

4) While using CCV,.


Actual results:

Fails to execute the subscription-manager commands on the hosts after the Satellite 6.14 upgrade.

Expected results:

Should be able to run the subscription manager or insights client without any errors.

Additional info:

   And we have identified the workaround and documented it at https://access.redhat.com/solutions/7048678.

Comment 2 Ian Ballou 2024-02-16 19:36:23 UTC

Changing component to Pulp since the error relates to what's in the Pulp DB.

This BZ may be related, as noted in one of the community posts https://bugzilla.redhat.com/show_bug.cgi?id=2149138#c2

Comment 3 Daniel Alley 2024-05-30 05:16:00 UTC

I think the tags on this issue got a bit mixed up.  It should have been +sat-6.15.0, +sat-6.14.z,  but instead it was ?sat-6.16.0, +sat-6.15.z, +sat-6.14.z

The issue is already fixed in 6.15.0, because the fix is present in pulp-rpm-3.23.1, and 6.15.0 has pulp-rpm-3.23.3

Comment 4 Eric Helms 2024-06-06 17:02:54 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 5 Red Hat Bugzilla 2024-10-05 04:27:17 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days