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.

Created from redmine issue http://projects.theforeman.org/issues/7833

We need to deploy this setting in the proxy YAML config file:

  :foreman_url: https://FQDN

The abrt and openscap plugins rely on this.

Connecting redmine issue http://projects.theforeman.org/issues/7833 from this bug

Moving to POST since upstream bug http://projects.theforeman.org/issues/7833 has been closed
-------------
Ewoud Kohl van Wijngaarden
That is the easiest. https://github.com/theforeman/puppet-foreman/blob/master/manifests/params.pp#L5 does the same. Then users who deploy it by default at least get a sane install.
-------------
Dominic Cleal
https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/params.pp#L174-L175 :)
-------------
Anonymous
Applied in changeset commit:puppet-foreman_proxy|7b70805aa0199bf53d9f621912fba4604bd835d8.

This bug is slated to be released with Satellite 6.1.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592