Connecting redmine issue http://projects.theforeman.org/issues/10725 from this bug

Upstream bug assigned to jsherril

Moving to POST since upstream bug http://projects.theforeman.org/issues/10725 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|313d22361610722afd50f2ed147865c0ae31cf5c.

NOTE: this will need an additional fix backported to downstream

additional fix needed:  https://github.com/Katello/katello/pull/5316

Delivered in Snap10

Hi,

   please provide verification steps
   thanks in advance

Thanks and Regards,
Tazim

This was described in an email recently, re-pasting here:


The way it was added was such that any action that requires one or more backend services, will have just those backend services checked.  Because of this I can't give you an exhaustive list, but I can give you a short list of the major actions:

Candlepin: Pulp & ES:
Content View Publish
Content view Promote
Content View Version Remove
Repo create
Repo destroy
Repo enable

Pulp & ES:
Repo Sync

Candlepin & ES only:
Product create
Organization Create


For checking with candlepin or elasticsearch, simply shutting down tomcat/tomcat6 or elasticsearch is good enough.

For testing pulp, you can try shutting down mongod, qpidd, pulp_workers, or pulp_celerybeat

I believe this is a delay before pulp realizes that workers disappear (like 60 seconds or so), but I am unsure.  It wouldn't surprise me if you find some bugs in the pulp detection of worker health.

VERIFIED:
# rpm -qa | grep foreman
foreman-proxy-1.7.2.5-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-client-1.0-1.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-1.0-2.noarch
foreman-gce-1.7.2.30-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-debug-1.7.2.30-1.el7sat.noarch
foreman-postgresql-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.17-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
foreman-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.18-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-compute-1.7.2.30-1.el7sat.noarch
foreman-vmware-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-libvirt-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch
puppet-foreman_scap_client-0.3.3-9.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-ovirt-1.7.2.30-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch


steps:

stop pulp, candlepin and elasticsearch services 

# hammer product create --name tp --organization-id 1
[Foreman] Username: admin
[Foreman] Password for admin: 
Could not create the product:
  There was an issue with the backend service candlepin: Connection refused - connect(2)

# hammer content-view create --name con_t --organization-id 1
[Foreman] Username: admin
[Foreman] Password for admin: 
Could not create the content view:
  Connection refused - connect(2)

This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.