Bug 2104830

Summary:	If searched for a non existent component, the package edit search shows an empty package icon instead of a "no package found" message.
Product:	Red Hat Enterprise Linux 9	Reporter:	Mohammed Salih <mputhenp>
Component:	cockpit-composer	Assignee:	Jacob <jkozol>
Status:	CLOSED MIGRATED	QA Contact:	Yi He <yih>
Severity:	low	Docs Contact:
Priority:	low
Version:	9.0	CC:	thozza
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
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:	2023-09-18 12:41:45 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 Mohammed Salih 2022-07-07 08:53:08 UTC

Description of problem:
In image builder GUI, while searching for a package, if there is no matching package, it should show an empty list, rather than an empty package block. It is confusing. I have attached an image for more clarity. And if you try to add this empty package block, it rightly gives an error, which some times leads to a blank page on the right and "ooops" message on the top. 

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


How reproducible:
Always

Steps to Reproduce:
1. Install image builder on a RHEL 9 VM, enable cockpit and osbuilder
2. Open the cockpit UI
3. Click on "Image Builder" shown on the left navigation pane
4. Create a blueprint, name it anything
5. In the following screen, search for a non existent component.
6. you should see package icon with a "+". It will not have any name on it.

Actual results:
A bogus package with a call for adding to the blueprint components.

Expected results:
Empty List, with a message similar to "No such component found"

Comment 2 RHEL Program Management 2023-09-18 12:39:35 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-18 12:41:45 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 "RHEL-" 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.