Bug 2122453

Summary:	edge-installer fail on blueprint with a hostname and cannot remove it in the wizard
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:	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 04:54:59 UTC

Description of problem:
When building edge-installer image, user cannot set hostname in the create wizard, this is correct because edge-installer does not support it. But, if the blueprint already has a hostname, for example, customer set the hostname when building other images, and now they will always fail with try to build edge-installer image, and there is no error message to indicate what's going wrong.

The only thing they can do, is to create other types of image, and remove the hostname, save the blueprint, and  then go back to create edge-installer again.

We better fix it, but in one hand we should not allow customer to set/edit/remove hostname in create wizard, and in the other hand, customer also cannot remove it if the blueprint already have the hostname.


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 19:03:09 UTC

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

Comment 2 RHEL Program Management 2023-09-18 12:39:58 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: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.