Feature #13683
closed[RFE] unattended_url needs to be a per-subnet setting
Description
Current use-case is a system (Satellite 6) with central Satellite server and several Capsules. At least one Capsule is located behind a firewall for the DMZ clients. These clients have no sight of the Satellite or any other Capsules. The current unattended_url is a global setting, so we need to change it every time we prepare a deployment in a different network area.
To compound this, part of our DMZ has no DNS available, so we currently need to set the unattended_url with IP address rather than FQDN. This particular problem may be better solved by other means, but changing the unattended_url is our current method. But the IP address that we need to use is behind a firewall from most of our clients.
Allowing the unattended_url to be set on a per-subnet basis will allow us to point deployments at the relevant Capsule more easily.
Updated by Dominic Cleal almost 9 years ago
- Is duplicate of Feature #1970: Override the foreman_url hostname added
Updated by Dominic Cleal almost 9 years ago
- Status changed from New to Duplicate
- Translation missing: en.field_release deleted (
123)
Feature is known already as #1970. Please don't set the target release field on new tickets, only found in release.
Updated by Duncan Innes almost 9 years ago
Sorry - thought I was setting a "version found in" field there.
Had searched issues on "unattended_url", so missed the one about "foreman_url"
Updated by Lukas Zapletal over 6 years ago
I have written an extensive post in https://bugzilla.redhat.com/show_bug.cgi?id=1307107 and made it public. Several workarounds are described there.