Project

General

Profile

Actions

Bug #26594

closed

[E] Could not fetch capabilities: hostname "localhost" does not match the server certificate

Added by Evgeni Golov about 5 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

on current (2019-04-11) nightly, when refreshing the features of a proxy, I see "[E] Could not fetch capabilities: hostname "localhost" does not match the server certificate" in /var/log/foreman-proxy/proxy.log

This surely does not smell right? :)

Actions #1

Updated by Ewoud Kohl van Wijngaarden about 5 years ago

Pretty sure that's from smart_proxy_pulp where Pulp 3: https://github.com/theforeman/smart_proxy_pulp/blob/3e4494cd745eb4822e178e079fdff2444cf8ec61/lib/smart_proxy_pulp_plugin/pulp3_client.rb#L16-L22

Should be safe, but it's a sign we need to expand puppet-foreman_proxy to handle the pulp3 config file as well so we can disable the plugin by default.

Actions #2

Updated by Samir Jha about 5 years ago

  • Project changed from Katello to Smart Proxy
Actions #3

Updated by Ewoud Kohl van Wijngaarden almost 5 years ago

  • Status changed from New to Rejected

By default we now disable the pulp3 plugin in the installer and it's also not part of the proxy itself so closing this.

Actions

Also available in: Atom PDF