Bug #9200
closedForeman discovery does not work with develop/master (Foreman 1.8/Katello 2.2.)
Updated by The Foreman Bot almost 10 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/4971 added
- Pull request deleted (
)
Updated by Bryce Nordgren almost 10 years ago
Can you be more specific about "does not work"? Is your problem identical with the problem I reported on the email list or is it different? My problem is that smart proxy/capsule requires a client SSL cert while the discovery image is hardcoded not to use one... (https://groups.google.com/forum/#!topic/foreman-users/IUXx_ZkKlU4)
From the email list:
- Foreman-proxy/capsule and the foreman discovery image are not compatible. (See http://projects.theforeman.org/issues/7822 and https://github.com/theforeman/foreman-discovery-image/blob/master/root/usr/bin/discovery-register#L47)
- The katello installer has no options for controlling whether the capsule uses SSL or not, so you can't make them compatible even for a test.
- You have to point the proxy.url at foreman itself, not the proxy/capsule. proxy.type needs to be "foreman"
To fix 1, I assume the installer would be required to issue a certificate to the foreman discovery image, then install it in the image, then build the image from scratch. Changes to the discovery-register code would also be required.
At the very least, pointing at the foreman instance instead of the proxy should be integrated into the process documented here: https://github.com/theforeman/foreman_discovery. Once the discovery-register code has been fixed, a manual process for installing a recognized certificate in the foreman discovery image could be added.
Updated by Eric Helms over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello-installer|c2862622dfdc841d62f156d4ca4081624f7fbb1c.