Bug 2122454

Summary:	cockpit-composer should return more useful error message when failed to create ostree image
Product:	Red Hat Enterprise Linux 9	Reporter:	Yi He <yih>
Component:	cockpit-composer	Assignee:	Jacob <jkozol>
Status:	CLOSED MIGRATED	QA Contact:	Yi He <yih>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	miabbott, rmetrich, thozza
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
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 12:42:11 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 Yi He 2022-08-30 05:03:28 UTC

Description of problem:
when create edge-installer on the blueprint with a hostname, the image creation will fail, but the return error message is just a popup saying 'image create failed', that's not enough for customer to understand what's going wrong, only if they are very familiar with ostree images.

For example, the same case in command line with get error message like "unsupported blueprint customizations found for boot ISO image type "edge-installer": (allowed: User, Group)"

This error message is also not very detailed, but it at least, let me know that something is wrong with customizations in blueprint.

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


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jacob 2022-09-06 18:54:08 UTC

*** Bug 2109223 has been marked as a duplicate of this bug. ***

Comment 2 Jacob 2022-09-06 18:59:42 UTC

*** Bug 2015810 has been marked as a duplicate of this bug. ***

Comment 3 RHEL Program Management 2023-09-18 12:39:56 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 4 RHEL Program Management 2023-09-18 12:42:11 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.