Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2196646

Summary:	Image Builder acts as if it is not installed, when looking in Cockpit UI, after upgrade to RHEL 9.2
Product:	Red Hat Enterprise Linux 9	Reporter:	Aaron Kulbe <aaron>
Component:	cockpit-composer	Assignee:	Jacob <jkozol>
Status:	CLOSED MIGRATED	QA Contact:	Yi He <yih>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	jkozol, mpitt, obudai
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 13:50:14 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 Aaron Kulbe 2023-05-09 17:28:43 UTC

Description of problem: Image Builder showing up as not installed even though it is already installed and has been used previously.


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


How reproducible: consistently


Steps to Reproduce:
1. Open up Cockpit
2. Click on "Image Builder", and observe that it is currently installed, and images from previous use already show up.
3. Click on Applications and observe that "Image Builder" shows up as if it is not installed, and you are presented with an "Install" button.
4. Click on "Install" and be presented with an error a about cockpit-composer already being installed.

Actual results:
Error message that says "cockpit-composer" is already installed.


Expected results:
"Image Builder" would still show up as if it were already installed.

I recorded a video that demonstrates what I'm seeing. There is no audio, just video, and it's 0m:39s long.  https://youtu.be/S3CxQqk4JHs


Additional info:

Comment 1 Ondřej Budai 2023-05-10 07:33:29 UTC

I can reproduce this as well.

@mpitt: Do you any idea why this is happening? Did something change in cockpit, or did we break something in cockpit-composer?

Comment 2 Martin Pitt 2023-05-10 08:08:11 UTC

I reproduced this on a clean RHEL 9.2 image, with its minimal cockpit 286.1-1.el9 packages (from the default install). I installed cockpit-packagekit in addition, and after a refresh on the Apps page, I get a bunch of packages offered for "Install" like "Image Builder", "Podman", "Machines", etc. That is right, none of these packages are installed (except for Subscription Manager).

I click "Install" on "Image builder", it appears in the menu, but the state indeed remains at "Install". This is not the case for e.g. "Podman", after installation it correctly switches to "Remove".

The problem is rather stupid, I'm afraid:

/usr/share/metainfo/io.weldr.cockpit-composer.metainfo.xml: xml.etree.ElementTree.ParseError: XML or text declaration not at start of entity: line 2, column 0

Indeed /usr/share/metainfo/io.weldr.cockpit-composer.metainfo.xml has a blank empty line at the start [1]. When I remove this, the Cockpit UI immediately moves to "Remove", i.e. it recognizes that it is installed (and it uses inotify to refresh on file changes).

This gets aggravated by the fact that `appstream-util validate-relax --nonet *.metainfo.xml` does not complain about the extra newline. cockpit-composer does not even use that (starter-kit does -- please consider donig that, as it will find other problems), but apparently Python's etree parser is stricter than libappstream's. xmllint does, though:

❱❱❱ xmllint public/io.weldr.cockpit-composer.metainfo.xml
public/io.weldr.cockpit-composer.metainfo.xml:2: parser error : XML declaration allowed only at the start of the document
<?xml version="1.0" encoding="UTF-8"?>

[1] https://github.com/osbuild/cockpit-composer/blob/377d071c8c76ee/public/io.weldr.cockpit-composer.metainfo.xml

Comment 3 Ondřej Budai 2023-05-10 08:21:55 UTC

Thanks, Martin, for such a quick investigation!

FTR, this is the commit that introduced the new newline: https://github.com/osbuild/cockpit-composer/commit/1713a0f5f61eed5c07448cb26b00fb2319d27953

Comment 4 RHEL Program Management 2023-09-18 13:48:23 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 5 RHEL Program Management 2023-09-18 13:50:14 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.