Project

General

Profile

Bug #15138

Start foreman-proxy on non-DHCP network

Added by Lukas Zapletal almost 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Image
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman-discovery-image/pull/73
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

We need to have a valid (self-signed) https certificate for particular
primary interface. If there is none, we can't do much about it. We might
change to code and start the proxy anyway so it is accessible over HTTP
at least. Instead an IP address in the common name, we will provide
a constant string.

https://github.com/theforeman/foreman-discovery-image/blob/master/root/usr/bin/generate-proxy-cert#L13

Associated revisions

Revision 0e9e0ba0 (diff)
Added by Lukas Zapletal almost 7 years ago

Fixes #15138 - start proxy when IPv4 is not present

History

#1 Updated by Lukas Zapletal almost 7 years ago

This patch will enable users to use Discovery Image on non-DHCP networks or very slow DHCP services. To configure http, use Smart Proxy Discovery plugin and configure it to use http in /etc/foreman-proxy/settings.d/discovery.yml:

:node_scheme: http
:node_port: 8448

#2 Updated by The Foreman Bot almost 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-discovery-image/pull/73 added

#3 Updated by Anonymous almost 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF