Bug 2213905

Summary:	Satellite can wrongly indicate installable errata to host when packages updated belong to different repos on a CV and the repos are not in sync between each other
Product:	Red Hat Satellite	Reporter:	Joniel Pasqualetto <jpasqual>
Component:	Errata Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.12.4	CC:	ahumbe, iballou, rlavi, vchepkov
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:21:43 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 Joniel Pasqualetto 2023-06-09 20:28:26 UTC

Description of problem:

 - An ERRATA (let's call it E1) affects multiple multiple packages, distributed in more than one repository. Let's say package A from  repo R1 and package B from package R2
 - content host has installed a vulnerable version of package A from R1
 - repositories were not synced at the same moment. So, ERRATA E1 was imported on repository R2 but not yet on repository R1
 - A CV was published containing R1 and R2
 - Satellite says errata E1 is installable on the content host because package A is vulerable (based on information from E1). However, newer version from A is not present on R1 yet

As result, user sees an installable errata that can't be installed.


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

Observed on Satellite 6.12


Steps to Reproduce:

See description

Comment 2 Eric Helms 2024-06-06 16:21:43 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.