Bug 1180666

Summary:	Deploy foreman_url setting for proxy configuration
Product:	Red Hat Satellite	Reporter:	Martin Milata <mmilata>
Component:	Installation	Assignee:	Katello Bug Bin <katello-bugs>
Status:	CLOSED ERRATA	QA Contact:	Tazim Kolhar <tkolhar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	bbuckingham, bkearney, cwelton, mmilata, tkolhar
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/7833
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 05:21:43 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:
Bug Depends On:
Bug Blocks:	1161120

Description Martin Milata 2015-01-09 16:20:45 UTC

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.

Comment 2 Bryan Kearney 2015-01-12 17:42:36 UTC

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

Comment 3 Bryan Kearney 2015-01-12 19:05:36 UTC

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.

Comment 7 Bryan Kearney 2015-08-11 13:23:20 UTC

This bug is slated to be released with Satellite 6.1.

Comment 8 errata-xmlrpc 2015-08-12 05:21:43 UTC

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