Plugins » Katello

I don't know if you have the same issue, but I had this error and solved it by adding the capsule fqdn and ip to /etc/hosts on the main katello server.

After I did this, things worked without this error.

I have the same problem (3.2.0-rc4), and the issue is that the capsule installer doesn't wait for the local daemon on port 9090 to become available before subscribing itself to katello. The result is that the katello server queries the capsule... which is not up (yet), hence the connection refused.
If I relaunch the installer it works correctly, because the capsule is already up.
This didn't happen in 3.0 or 3.1, and depending on the relative speed of the hosts may not happen every time, as it's 99% a race condition betwee the capsule startup and the subscription to katello.

I have same issues with the rc4 every time to try add a capsule i just give it up and install 3.1 that looks more stable

Mario Gamboa wrote:

I have same issues with the rc4 every time to try add a capsule i just give it up and install 3.1 that looks more stable

A work around for this bug is to re-run the capsule installer

I ran into this as well during the 3.2 upgrade of my capsules.

Re-running had no effect, the installer wanted to restart the foreman-proxy service everytime.

My "solution" was to hack in a wait period. Seemed to help.

Changing /usr/share/foreman-installer/modules/foreman_proxy/manifests/register.pp:

--- register.pp 2017-01-24 12:49:13.981489759 -0600
+++ register.hack.pp    2017-01-24 12:49:05.494268892 -0600
@@ -2,6 +2,10 @@
 class foreman_proxy::register {

   if $foreman_proxy::register_in_foreman {
+    exec {"wait for proxy to be available":
+       require => Service["foreman-proxy"],
+       command => "/usr/bin/wget --spider --tries 10 --retry-connrefused --no-check-certificate $foreman_proxy::real_registered_proxy_url/pulpnode/status/puppet",
+    }
     foreman_smartproxy { $foreman_proxy::registered_name:
       ensure          => present,
       base_url        => $foreman_proxy::foreman_base_url,

i just get now same issues when try to upgrade to 3.3 from 3.1