Bug 2250736

Summary:	Package rubygem-dynflow not listed in a list of packages
Product:	Red Hat Satellite	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	Tasks Plugin	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.15.0	CC:	ahumbe, aruzicka, rlavi
Target Milestone:	Unspecified	Keywords:	EasyFix, 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:36:38 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 Lukáš Hellebrandt 2023-11-20 22:19:45 UTC

Description of problem:
In a list of packages in WebUI -> Administer -> About -> Installed packages, package rubygem-dynflow is not listed. It should be.

Version-Release number of selected component (if applicable):
Sat Stream 6.15 snap 37.0.

How reproducible:
Deterministic

Steps to Reproduce:
1. Go to WebUI -> Administer -> About

Actual results:
Installed packages don't contain rubygem-dynflow even though it's installed

Expected results:
Installed packages should contain rubygem-dynflow

Comment 2 Adam Ruzicka 2023-11-21 10:07:58 UTC

I believe #1 is relevant to BZ #2250732, not this one.

The fix for this should be really simple and even though it needs to happen in Katello, I'll keep the component as is.

Comment 4 Eric Helms 2024-06-06 16:36:38 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.