Bug #14805
SSL error registering capsule
Description
When I attempt to register a capsule with katello (2.4) I receive the following error: Proxy dns3-vm.sc.fsu.edu cannot be registered (422 Unprocessable Entity): Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([OpenSSL::SSL::SSLError]: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verif...) for proxy https://dns3-vm.sc.fsu.edu:9090/features Please check the proxy is configured and running on the host.
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[dns3-vm.sc.fsu.edu]/ensure: change from absent to present failed: Proxy dns3-vm.sc.fsu.edu cannot be registered (422 Unprocessable Entity): Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([OpenSSL::SSL::SSLError]: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verif...) for proxy https://dns3-vm.sc.fsu.edu:9090/features Please check the proxy is configured and running on the host.
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[dns3-vm.sc.fsu.edu]: Failed to call refresh: Proxy dns3-vm.sc.fsu.edu cannot be registered (ApipieBindings::MissingArgumentsError: id): N/A
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[dns3-vm.sc.fsu.edu]: Proxy dns3-vm.sc.fsu.edu cannot be registered (ApipieBindings::MissingArgumentsError: id): N/A
I received this error both when registering an existing capsule with a new katello server, and when registering a new capsule with a new katello server.
I can confirm that there are no firewall rules preventing communication between the two systems. Both systems are using CentOS 7.2 and the 2.4 katello repositories.
I have uploaded my capsule debug information here: http://debugs.theforeman.org/foreman-debug-TlkxX.tar.xz
History
#1
Updated by Eric Helms about 6 years ago
- Legacy Backlogs Release (now unused) set to 150
#2
Updated by Justin Sherrill almost 6 years ago
- Legacy Backlogs Release (now unused) changed from 150 to 144
#3
Updated by Eric Helms almost 6 years ago
- Legacy Backlogs Release (now unused) changed from 144 to 168
#4
Updated by Eric Helms almost 6 years ago
- Legacy Backlogs Release (now unused) changed from 168 to 171
#5
Updated by Eric Helms almost 6 years ago
- Legacy Backlogs Release (now unused) deleted (
171)
#6
Updated by Justin Sherrill almost 6 years ago
- Status changed from New to Need more information
Are you able to reproduce on a fresh system with a 3.0 capsule? Also did you run katello-remove at all on the katello server prior?
#7
Updated by Justin Sherrill almost 6 years ago
- Legacy Backlogs Release (now unused) set to 166
#8
Updated by Justin Sherrill almost 6 years ago
- Status changed from Need more information to Rejected