Bug 2128237

Summary: The value of "--foreman-foreman-url" option is not honored as the value of foreman_url in Satellite settings.
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.2CC: ehelms, peter.vreman
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 12:34:41 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 Sayan Das 2022-09-20 10:19:11 UTC 
Description of problem:

The value of "--foreman-foreman-url" option is not honored as the value of foreman_url in Satellite settings. 


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

Satellite 6.11.2


How reproducible:

Always ( but under very specific circumstances )


Steps to Reproduce:

1. Repeat Step 1 to Step 5 from BZ https://bugzilla.redhat.com/show_bug.cgi?id=2127955 as the reproducer steps. 

2. Once the installer finishes, Check the following outputs:

# hammer settings info --name foreman_url

# hammer settings info --name unattended_url

# grep url /etc/foreman-installer/scenarios.d/satellite-answers.yaml



Actual results:

The unattended_url is correctly set but not the foreman_url

# hammer settings info --name foreman_url 
Id:            foreman_url
Name:          foreman_url
Description:   URL where your Foreman instance is reachable (see also Provisioning > unattended_url)
Category:      General
Settings type: string
Value:         https://sat611.example.com

# hammer settings info --name unattended_url
Id:            unattended_url
Name:          unattended_url
Description:   URL hosts will retrieve templates from during build, when it starts with https unattended/userdata controllers cannot be accessed via HTTP
Category:      Provisioning
Settings type: string
Value:         https://mysatellite.example.com


Whereas the answers file shows that installer used the right values:

# grep url /etc/foreman-installer/scenarios.d/satellite-answers.yaml
  foreman_url: https://mysatellite.example.com
  unattended_url: https://mysatellite.example.com
  dynflow_redis_url: 
  foreman_url: 
  puppet_url: https://mysatellite.example.com:8140
  template_url: http://mysatellite.example.com:8000
  foreman_base_url: https://mysatellite.example.com
  registered_proxy_url: 
  source_url: http://downloads.theforeman.org/discovery/releases/latest/
  server_foreman_url: https://mysatellite.example.com


Expected results:

The  --foreman-foreman-url and\or --puppet-server-foreman-url should be honored when the value of foreman_url settings is being set. 


Additional info:

NA
Comment 4 Sayan Das 2023-04-21 13:53:51 UTC 

The installer option is defined in this way:

https://github.com/theforeman/puppet-foreman/blob/master/manifests/params.pp#L1-L7

class foreman::params inherits foreman::globals {
  $lower_fqdn = downcase($facts['networking']['fqdn'])

  # Basic configurations
  $foreman_url      = "https://${lower_fqdn}"


And the settings are defined in this way 

https://github.com/theforeman/foreman/blob/develop/app/registries/foreman/settings/general.rb#L12-L17

    setting('foreman_url',
      type: :string,
      description: N_("URL where your Foreman instance is reachable (see also Provisioning > unattended_url)"),
      default: "#{SETTINGS[:require_ssl] ? 'https' : 'http'}://#{SETTINGS[:fqdn]}",
      full_name: N_('Foreman URL'),
      validate: :http_url)

So they are not at all related to each other or dependent on each other.


But since the names are very similar to each other, The end-user had to assume that the installer option is not properly updating the value of the setting and hence the BZ.

If it makes any sense to have the installer option populate the setting value, then perhaps that is what the end-user is looking for. Otherwise, if there are any specific questions about this request or this BZ, I can get the answers collected from the user.
Comment 7 Brad Buckingham 2024-03-21 21:07:37 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 8 Sayan Das 2024-04-17 17:01:53 UTC 
There have been two questions raised by the end user here:

A) How does the functionality and use case of the "--foreman-foreman-url" differ from "Setting[:foreman_url]" i.e. how and where does the satellite use them individually?

B) If it's logically expected to have the same values in "--foreman-foreman-url" as well as "Setting[:foreman_url]" but this setting cannot be installer managed ( to maintain consistency ), Then is there a situation where the value of "Setting[:foreman_url]" can differ from the value passed with "--foreman-foreman-url" ?


-- Sayan
Comment 10 Brad Buckingham 2024-05-10 13:07:09 UTC 
Skipping auto-closure to allow for addressing of the questions raised afterwards; however, it may be closed in a future iteration.
Comment 12 Eric Helms 2024-06-06 12:34:41 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.
Comment 13 Red Hat Bugzilla 2024-10-05 04:25:30 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days