This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1686701 - [RFE] "Satellite server FQDN" should be default and frozen value.
Summary: [RFE] "Satellite server FQDN" should be default and frozen value.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: yanpliu
satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-08 03:42 UTC by yuefliu
Modified: 2024-06-05 21:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-05 21:31:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26319 0 Normal New "Satellite server FQDN" should be default and frozen value. 2020-06-19 10:26:40 UTC
Red Hat Issue Tracker   SAT-24580 0 None Migrated None 2024-06-05 21:31:12 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.