Bug 1686701

Summary:	[RFE] "Satellite server FQDN" should be default and frozen value.
Product:	Red Hat Satellite	Reporter:	yuefliu <yuefliu>
Component:	Virt-who Configure Plugin	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED MIGRATED	QA Contact:	yanpliu <yanpliu>
Severity:	medium	Docs Contact:	satellite-doc-list
Priority:	unspecified
Version:	6.5.0	CC:	chrobert, iballou, kuhuang, mhulan, yanpliu, yuefliu
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Reopened
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-05 21:31: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:

Comment 2 Marek Hulan 2019-03-08 07:29:06 UTC

Why do you think it should be frozen? What if people don't have the url set correctly in Satellite? What if they need to use different name on some machines (multihoming use case). If they couldn't change the value, I think we should rather not show that at all.

Comment 3 Eko 2019-03-08 07:38:23 UTC

Hi Marek, I think yuefliu's point is:

if the "Satellite server FQDN" is changed to other satellite server, the rhsm_username and rhsm_password should be changed together.
because maybe there are no account(rhsm_username=virt_who_reporter_1) in the other satellite server.

Comment 4 Marek Hulan 2019-03-08 11:52:45 UTC

So in other words, we should disable editing after it has been once created? What if people change the Satellite hostname later?

Comment 8 Marek Hulan 2019-03-12 13:39:38 UTC

Created redmine issue https://projects.theforeman.org/issues/26319 from this bug

Comment 9 Bryan Kearney 2020-05-01 14:15:02 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Comment 10 Ian Ballou 2024-04-15 15:26:00 UTC

Closed prematurely -- reopening to address very soon.

Comment 11 Eric Helms 2024-05-16 16:16:00 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/26319 has been resolved.

Comment 12 Eric Helms 2024-06-05 21:31: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 "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.